Method and system for performing an authentication and authorization operation on video data using a data processing unit

ABSTRACT

A method for processing video data is performed by a data processing unit (DPU). The method includes obtaining, by a data processing unit (DPU) of an edge device, video data; processing the video data to obtain video data chunks and video processing engine outcomes; generating authentication and authorization (AA) metadata based on the video data chunks and the video processing engine outcomes; associating the AA metadata with the video data chunks based on the video processing outcomes; and storing the AA metadata and the video data chunks.

BACKGROUND

Devices may obtain data from other devices and generate informationbased on the obtained data. The generated information may be associatedwith the obtained data. The obtained data and generated information maybe stored in storage devices. To obtain data and store data, devices maybe able to communicate with other devices. The communications betweendevices may be through any means. The devices may be connected via anycombination of wireless and non-wireless connections.

SUMMARY

In general, in one aspect, the invention relates to a method performedto process video data. The method includes obtaining, by a dataprocessing unit (DPU) of an edge device, video data; processing thevideo data to obtain video data chunks and video processing engineoutcomes; generating authentication and authorization (AA) metadatabased on the video data chunks and the video processing engine outcomes;associating the AA metadata with the video data chunks based on thevideo processing outcomes; and storing the AA metadata and the videodata chunks.

In general, in one aspect, the invention relates to a system that isused to process video data. The system includes a backup storageoperatively connected to an edge device, a video camera operativelyconnected to the edge device and configured to generate video data, theedge device, which includes a data processing unit (DPU). The DPU isconfigured to perform a method. The method includes obtaining, by theDPU of an edge device, video data; processing the video data to obtainvideo data chunks and video processing engine outcomes; generatingauthentication and authorization (AA) metadata based on the video datachunks and the video processing engine outcomes; associating the AAmetadata with the video data chunks based on the video processingoutcomes; and storing the AA metadata and the video data chunks.

In general, in one aspect, the invention relates to a non-transitorycomputer readable medium which includes computer readable program code,which when executed by a computer processor enables the computerprocessor to perform a method for processing video data. The methodincludes obtaining, by a data processing unit (DPU) of an edge device,video data; processing the video data to obtain video data chunks andvideo processing engine outcomes; generating authentication andauthorization (AA) metadata based on the video data chunks and the videoprocessing engine outcomes; associating the AA metadata with the videodata chunks based on the video processing outcomes; and storing the AAmetadata and the video data chunks.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1A shows a diagram of a system in accordance with one or moreembodiments of the invention.

FIG. 1B shows a diagram of an edge device in accordance with one or moreembodiments of the invention.

FIG. 1C shows a diagram of a backup storage in accordance with one ormore embodiments of the invention.

FIG. 2A shows a diagram of video metadata in accordance with one or moreembodiments of the invention.

FIG. 2B shows a diagram of processed video data in accordance with oneor more embodiments of the invention.

FIG. 3A shows a flowchart of a method for performing an indexingoperation on video data in accordance with one or more embodiments ofthe invention.

FIG. 3B shows a diagram of a first example in accordance with one ormore embodiments of the invention.

FIG. 4A shows a flowchart of a method for performing a contextualoperation on video data in accordance with one or more embodiments ofthe invention.

FIG. 4B shows a diagram of a second example in accordance with one ormore embodiments of the invention.

FIG. 5A shows a flowchart of a method for performing storage tieroperation on video data in accordance with one or more embodiments ofthe invention.

FIG. 5B shows a diagram of a third example in accordance with one ormore embodiments of the invention.

FIG. 6A shows a flowchart of a method for performing a complianceoperation on video data in accordance with one or more embodiments ofthe invention.

FIG. 6B shows a diagram of a fourth example in accordance with one ormore embodiments of the invention.

FIG. 7A shows a flowchart of a method for performing an authenticationand authorization operation on video data in accordance with one or moreembodiments of the invention.

FIG. 7B shows a diagram of a fifth example in accordance with one ormore embodiments of the invention.

FIG. 8A shows a flowchart of a method for performing a long termstitching operation on video data in accordance with one or moreembodiments of the invention.

FIGS. 8B-8C show diagrams of a sixth example in accordance with one ormore embodiments of the invention.

FIG. 9A shows a flowchart of a method for performing a contextualstitching operation on video data in accordance with one or moreembodiments of the invention.

FIG. 9B shows a diagram of a seventh example in accordance with one ormore embodiments of the invention.

FIG. 10A shows a flowchart of a method for performing a right to beforgotten operation on video data in accordance with one or moreembodiments of the invention.

FIG. 10B shows a diagram of an eighth example in accordance with one ormore embodiments of the invention.

FIG. 11 shows a diagram of a computing system in accordance with one ormore embodiments of the invention.

DETAILED DESCRIPTION

Specific embodiments of the invention will now be described in detailwith reference to the accompanying figures. Like elements in the variousfigures are denoted by like reference numerals for consistency. In thefollowing description, numerous details are set forth as examples of theinvention. It will be understood by those skilled in the art that one ormore embodiments of the present invention may be practiced without thesespecific details and that numerous variations or modifications may bepossible without departing from the scope of the invention. Certaindetails known to those of ordinary skill in the art are omitted to avoidobscuring the description.

In the following description of the figures, any component describedwith regard to a figure, in various embodiments of the invention, may beequivalent to one or more like-named components described with regard toany other figure. For brevity, descriptions of these components will notbe repeated with regard to each figure. Thus, each and every embodimentof the components of each figure is incorporated by reference andassumed to be optionally present within every other figure having one ormore like-named components. Additionally, in accordance with variousembodiments of the invention, any description of the components of afigure is to be interpreted as an optional embodiment, which may beimplemented in addition to, in conjunction with, or in place of theembodiments described with regard to a corresponding like-namedcomponent in any other figure.

Throughout this application, elements of figures may be labeled as A toN. As used herein, the aforementioned labeling means that the elementmay include any number of items and does not require that the elementinclude the same number of elements as any other item labeled as A to N.For example, a data structure may include a first element labeled as Aand a second element labeled as N. This labeling convention means thatthe data structure may include any number of the elements. A second datastructure, also labeled as A to N, may also include any number ofelements. The number of elements of the first data structure and thenumber of elements of the second data structure may be the same ordifferent.

In general, embodiments of the invention relate to generatingauthentication and authorization (AA) metadata based on video processingengine outcomes through authentication and authorization operations wheninitially processing video data by a data processing unit (DPU) of anedge device. Further, in various embodiments of the invention, AAmetadata may be used by the DPU to store and manage video data inaccordance with authentication and authorization requirements specifiedby the AA metadata. Additionally, the AA metadata may specify if videodata is associated with legal holds.

Turning to the figures, FIG. 1A shows a diagram of a system inaccordance with one or more embodiments of the invention. The system mayinclude edge devices (100) and backup storages (120). The edge devices(100) may include one or more edge devices, e.g., edge device A (100A),edge device B (100B), and edge device N (100N). The backup storages(120) may include one or more backup storages, e.g., backup storage A(120A), backup storage B (120B), and backup storage N (120N). The systemmay include video cameras (not shown). The video cameras may be devicesthat record visual and/or audio data and provide the video and/or audiodata to the edge devices (100). The system may include additional,fewer, and/or different components without departing from the invention.Each of the aforementioned components is discussed below.

In one or more embodiments of the invention, the video cameras areconnected to the edge devices through a local connection. The devices(e.g., one or more video cameras and one or more edge devices) in alocal connection may share the same geographic location. The localconnection may be a local area network (LAN). The devices in the LAN maybe connected, for example, through the Transmission Control Protocol(TCP) and Internet Protocol (IP) Ethernet connections or Wi-Fi. Further,the local connection may encompass various interconnected,network-enabled subcomponents (or systems) (e.g., switches, routers,gateways, etc.) (not shown) that may facilitate communications betweenthe above-mentioned devices of the local connection. The localconnection may be another type of local area network and/or may beimplemented with other and/or additional connections, devices, and/orprotocols without departing from the invention.

In one or more embodiments of the invention, the edge devices (100) areconnected to the backup storages (120) through a non-local connection.The devices (e.g., one or more edge devices and one or more backupstorages) in a non-local connection may span any number of geographiclocations of any size without departing from the invention. Thenon-local connection may be, for example, one or more wide area networks(WANs) such as the Internet. A WAN may connect any number of localconnections to allow communications and data transmission from onegeographic location to another. The WAN may encompass variousinterconnected, network-enabled subcomponents (or systems) (e.g.,switches, routers, gateways, etc.) (not shown) that may facilitatecommunications between the above-mentioned non-local connection devices.Moreover, the non-local connection components and devices maycommunicate with one another using any combination of wired and/orwireless communication protocols. The non-local connection may beanother type of network connection spanning multiple geographiclocations and/or may be implemented with other and/or additionalconnections and/or devices without departing from the invention.

In one or more embodiments of the invention, the edge devices (100)include the functionality to process video data obtained from videocameras and/or backup storages (120). The edge devices may also includethe functionality to manage the storage and provision of video data toand from video cameras, backup storages (120), and/or users (not shown)of the system. For additional information regarding the edge devices(100), refer to FIG. 1B.

In one or more embodiments of the invention, each of the edge devices(100) is implemented as a computing device (see e.g., FIG. 11). Thecomputing device may be, for example, a mobile phone, a tablet computer,a laptop computer, a desktop computer, a server, a distributed computingsystem, or a cloud resource. The computing device may include one ormore processors, memory (e.g., random access memory), and persistentstorage (e.g., disk drives, solid state drives, etc.). The computingdevice may include instructions, stored on the persistent storage, thatwhen executed by the processor(s) of the computing device cause thecomputing device to perform the functionality of an edge device (e.g.,100A) described throughout this application.

In one or more embodiments of the invention, each of the edge devices(100) is implemented as a logical device. The logical device may utilizethe computing resources of any number of computing devices and therebyprovide the functionality of the edge devices (100) described throughoutthis application.

In one or more embodiments of the invention, the backup storages (120)include the functionality to store video data and video metadataobtained from the edge devices (100). The backup storages (120) may alsoinclude the functionality to provide video data to the edge devices(100). For additional information regarding the backup storages (120),refer to FIG. 1C.

In one or more embodiments of the invention, each of the backup storages(120) is implemented as a computing device (see e.g., FIG. 11). Thecomputing device may be, for example, a mobile phone, a tablet computer,a laptop computer, a desktop computer, a server, a distributed computingsystem, or a cloud resource. The computing device may include one ormore processors, memory (e.g., random access memory), and persistentstorage (e.g., disk drives, solid state drives, etc.). The computingdevice may include instructions, stored on the persistent storage, thatwhen executed by the processor(s) of the computing device cause thecomputing device to perform the functionality of a backup storage (e.g.,120A) described throughout this application.

In one or more embodiments of the invention, each of the backup storages(120) is implemented as a logical device. The logical device may utilizethe computing resources of any number of computing devices and therebyprovide the functionality of the backup storages (120) describedthroughout this application.

FIG. 1B shows a diagram of an edge device in accordance with one or moreembodiments of the invention. Edge device A (100A) may be an embodimentof an edge device (e.g., 100A, FIG. 1A) discussed above. As discussedabove, edge device A (100A) may include the functionality to processvideo data and manage the storage and provision of video data to andfrom users, video cameras, and backup storages (120, FIG. 1A). Edgedevice A (100A) may include a peripheral interface(s) (102), a dataprocessing unit (DPU) (104), and edge storage (112). Edge device A(100A) may include additional, fewer, and/or different componentswithout departing from the invention. Each of the aforementionedcomponents is discussed below.

In one or more embodiments of the invention, the peripheral interface(s)(102) include the functionality to facilitate communications betweenedge device A (100A) and one or more video cameras (not shown in thesystem illustrated in FIG. 1A. There may be one or more peripheralinterfaces (102) providing communications between one or more videocameras and edge device A (100A) without departing from the invention.The peripheral interface(s) (102) may include any type of communicationinterface that enables a physical or wireless connection to beestablished between the edge device A (100A) and another device (i.e.,video camera). The peripheral interface(s) (102) may be implementedusing a combination of physical ports and corresponding hardware and/orsoftware. The specific hardware and/or software used to implement thecommunication interfaces may vary based on the communication protocolused. Examples of communication protocols include, but are not limitedto, Ethernet and Infiniband.

In one or more embodiments of the invention, the peripheral interface(s)(102) is a physical device. The physical device may include circuitry.The physical device may be, for example, a field-programmable gatearray, application specific integrated circuit, programmable processor,microcontroller, digital signal processor, or other hardware processor.The physical device may be adapted to provide the functionality of theperipheral interface(s) (102) described throughout this application.

In one or more embodiments of the invention, the peripheral interface(s)(102) is implemented as computer instructions, e.g., computer code,stored on a persistent storage that when executed by a processor of edgedevice A (100A) causes edge device A (100A) to provide the functionalityof the peripheral interface(s) (102) described throughout thisapplication.

In one or more embodiments of the invention, the DPU (104) includes thefunctionality to process video data. The DPU (104) may process videodata via indexing operations, contextual operations, storage tieroperations, compliance operations, authentication and authorizationoperations, long term stitching operations, contextual stitchingoperations, and right to be forgotten (RTF) operations. The DPU mayinclude the functionality to perform other types of video dataprocessing operations (e.g., deduplication and erasure coding) withoutdeparting from the invention. Each of these operations is discussedbelow.

An indexing operation may refer to generating indexing metadata(discussed below) associated with video data obtained from a videocamera and/or a backup storage (e.g., 120A). The indexing metadata mayinclude indexing information associated with the video data. Theindexing information may specify information regarding the video datachunks of the video data such as start times, end times, subjectsincluded in the video data, and objects included in the video data. Theindexing information may include other information regarding the videodata without departing from the invention. The indexing metadata mayenable efficient searching of relevant video data chunks stored inbackup storages (120, FIG. 1A). For additional information regarding theindexing operation, refer to FIG. 3A.

A contextual operation may refer to generating contextual metadata(discussed below) associated with video data obtained from a videocamera and/or a backup storage (e.g., 120A). The contextual metadata mayinclude contextual information associated with video data chunks. Thecontextual information may include, for example, what emotion(s) areshown by a person, actions taken by a person, and other and/oradditional contextual information associated with video data withoutdeparting from the invention. The contextual metadata may furtheroptimize the searching of video data stored in backup storages (120,FIG. 1A). For additional information regarding a contextual operation,refer to FIG. 4A.

A storage tier operation may refer to generating storage tier metadata(discussed below) associated with video data obtained from a videocamera and/or a backup storage (e.g., 120A). The storage tier metadatamay specify storage types video data chunks of the video data are to bestored in based on the video data chunk content. The storage tiermetadata may be used to store highly relevant video data chunks infast-access storage and less relevant data in more cost-effectivestorage. The storage tier metadata may allow the DPU (104) toefficiently store the video data in backup storages (120, FIG. 1A). Foradditional information regarding a storage tier operation, refer to FIG.5A.

A compliance operation may refer to generating compliance metadata(discussed below) associated with video data obtained from a videocamera and/or a backup storage (e.g., 120A). The compliance metadata mayspecify compliance requirements associated with video data chunks of thevideo data based on the video data chunk content. The compliancemetadata may be used to efficiently store video data chunks in backupstorages (120, FIG. 1A) while following compliance requirementsassociated with the video data. For additional information regarding acompliance operation, refer to FIG. 6A.

An authentication and authorization (AA) operation may refer togenerating (AA) metadata (discussed below) associated with video dataobtained from a video camera and/or a backup storage (e.g., 120A). TheAA metadata may specify authentication and authorization informationassociated with video data. The AA metadata may be used to ensureauthorized users are able to access video data stored in backup storages(120, FIG. 1A) and the type of access that each authorized user has. TheAA metadata may improve the security of the video data stored in backupstorages (120, FIG. 1A). For additional information regarding an AAoperation, refer to FIG. 7A.

A long term stitching operation may refer to generating retention andstaging metadata (discussed below) associated with video data obtainedfrom a video camera and/or a backup storage (e.g., 120A). The retentionand staging metadata may specify storage types and retention periodsassociated with video data. The retention and staging metadata may beused to efficiently store video data stored in backup storages (120,FIG. 1A), properly de-stage video data from one type of storage toanother, and to stitch video data chunks of the video data when thevideo data chunks are all de-staged to archival storage. For additionalinformation regarding an AA operation, refer to FIG. 8A.

A contextual stitching operation may refer to searching for video datachunks stored in backup storages (120, FIG. 1A) and providing video datachunks to users. The DPU (104) may search for video data chunks based onindexing metadata and/or contextual metadata, and may use the AAmetadata associated with the video data chunks to ensure that onlyauthorized users are enables to view the video data chunks. A contextualstitching operation may improve the efficiency and security of searchingfor and providing video data to users of the system. For additionalinformation regarding a contextual stitching operation, refer to FIG.9A.

A right to be forgotten (RTF) operation may refer to deleting video dataof people who are not associated with any wrongdoing. The DPU (104) mayefficiently search for and obtain video data associated with a personusing indexing metadata and contextual metadata, and may determine anywrongdoing associated with the video data. The DPU (104) may verify anywrongdoing with users of the system. The DPU (104) may delete the datachunks if the wrongdoing is cleared by the users or may reject the RTFrequest if the wrongdoing is not cleared by the users. A RTF operationenables support of privacy laws while also mitigating the deletion ofvideo data chunks associated with wrongdoing. For additional informationassociated with RTF operations, refer to FIG. 10A.

In one or more embodiments of the invention, any given DPU (e.g., 104)includes the functionality to perform any combination of the operationsdepicted in FIGS. 3A-10B below independently without departing from theinvention. For example, a first DPU may only perform indexingoperations, contextual operations, and contextual stitching operations.A second DPU may only perform storage tier operations, complianceoperations, AA operations, and contextual stitching operations. A thirdDPU may perform all of the aforementioned operations.

The DPU (104) may perform the operations depicted below and generate,manage, and use the different types of metadata generated throughperforming the operations depicted below in a coexisting manner.

To provide the aforementioned functionality of the DPU (104), the DPU(104) may include a video processing engine (106), a context generator(108), and a virtual blob generator (110). The DPU (104) may includeadditional, fewer, and/or different components without departing fromthe invention. Each of the aforementioned components is discussed below.

In one or more embodiments of the invention, the video processing engine(106) includes the functionality to process video data obtained fromvideo cameras and/or backup storages (120, FIG. 1A) to obtain video datachunks and video processing engine outcomes. The video processing engine(106) may include one or more data analytics models (not shown). Thedata analytics models may be any models that may be applied to videodata and generate video data chunks and video processing engine outcomeswithout departing from the invention. The video processing engineoutcomes may be image classifications, object detections, and otherand/or additional video processing engine outcomes without departingfrom the invention. The data analytics models may be any one or moremachine learning models, artificial intelligence models, and/or deeplearning models that may be used for image classification and objectdetection (e.g., artificial neural networks) without departing from theinvention.

In one embodiment of the invention, the data analytics model(s) may begenerated and/or obtained from a user of the system and may executelocally on the DPU (104). The data analytics model(s) may be trainedwith (i) only training data obtained within the system, (ii) anycombination of third party training data and data obtained within thesystem, or (iii) only third party training data without departing fromthe invention. The data analytics model(s) may generate one or morevideo processing engine outcomes, indexing attributes, and/or one ormore video data chunks using video data obtained from the system.

In another embodiment of the invention, the data analytics model(s) maybe obtained from a third party and may execute remotely on third partydevices (not shown in the system of FIG. 1A). The data analyticsmodel(s) may be trained with (i) only training data obtained within thesystem, (ii) any combination of third party training data and dataobtained within the system, or (iii) only third party training datawithout departing from the invention. The DPU (104) may provide videodata to the data analytics model(s) executing on a third party device.The third party device may apply the data analytics model(s) to thevideo data to obtain one or more video processing engine outcomes,indexing attributes, and/or one or more video data chunks. The thirdparty devices may provide the video processing engine outcomes, indexingattributes, and the video data chunks to the DPU (104), and the DPU(104) may perform the aforementioned operations using the obtained videodata chunks, indexing attributes, and the video processing engineoutcomes.

In one or more embodiments of the invention, the video processing engine(106) is one or more physical devices. The physical device may includecircuitry. The physical device may be, for example, a field-programmablegate array, application specific integrated circuit, programmableprocessor, microcontroller, digital signal processor, or other hardwareprocessor. The physical device may be adapted to provide thefunctionality of the video processing engine (106) described throughoutthis application.

In one or more embodiments of the invention, the video processing engine(106) is implemented as computer instructions, e.g., computer code,stored on a persistent storage that when executed by a processor of edgedevice A (100A) or the DPU (104) causes edge device A (100A) or the DPU(104) to provide the functionality of the video processing engine (106)described throughout this application.

In one or more embodiments of the invention, the context generator (108)includes the functionality to generate contextual attributes associatedwith video data. The context generator (106) may also be used togenerate text transcripts associated with video data chunks. The contextgenerator (106) may include one or more context generation models. Thecontext generation models may include natural language processing modelsand/or body language detection models. The natural language processingmodels and body language detection models may be any mathematical models(e.g., artificial neural networks that include speech recognition andoptical character recognition) that generate contextual attributes(e.g., behavioral and/or linguistic characteristics of a subject)associated with video data without departing from the invention. Thecontext generator (106) may include other and/or additionalfunctionality without departing from the invention.

In one embodiment of the invention, the natural language processingmodels and/or body language detection models may be generated and/orobtained from a user of the system and may execute locally on the DPU(104). The natural language processing models and/or body languagedetection models may be trained with (i) only training data obtainedwithin the system, (ii) any combination of third party training data andtraining data obtained within the system, or (iii) only third partytraining data without departing from the invention. The natural languageprocessing models and/or body language detection models may generatecontextual attributes using video data obtained from the system.

In another embodiment of the invention, the natural language processingmodels and/or body language detection models may be obtained from athird party and may execute remotely on third party devices (not shownin the system of FIG. 1A). The natural language processing models and/orbody language detection models may be trained with (i) only trainingdata obtained within the system, (ii) any combination of third partytraining data and data obtained within the system, or (iii) only thirdparty training data without departing from the invention. The DPU (104)may provide video data and indexing attributes to the natural languageprocessing models and/or body language detection models executing on athird party device. The third party device may apply the naturallanguage processing models and/or body language detection models to thevideo data and indexing attributes to obtain contextual attributes. Thethird party devices may provide the contextual attributes to the DPU(104), and the DPU (104) may perform the one or more aforementionedoperations using the obtained contextual attributes. In one or moreembodiments of the invention, the context generator (108) is one or morephysical devices. The physical device may include circuitry. Thephysical device may be, for example, a field-programmable gate array,application specific integrated circuit, programmable processor,microcontroller, digital signal processor, or other hardware processor.The physical device may be adapted to provide the functionality of thecontext generator (108) described throughout this application.

In one or more embodiments of the invention, the context generator (108)is implemented as computer instructions, e.g., computer code, stored ona persistent storage that when executed by a processor of edge device A(100A) or the DPU (104) causes edge device A (100A) or the DPU (104) toprovide the functionality of the context generator (108) describedthroughout this application.

In one or more embodiments of the invention, the virtual blob generator(110) includes the functionality to generate virtual blobs associatedwith video data stored in backup storages (120, FIG. 1A). The virtualblob generator (110) may include the functionality to generate virtualblob files that include AA metadata, indexing metadata, and contextualmetadata associated with video data chunks using video data chunks, AAmetadata, indexing metadata, and contextual metadata. The virtual blobgenerator may include other and/or additional functionality withoutdeparting from the invention.

In one or more embodiments of the invention, the virtual blob generator(110) is one or more physical devices. The physical device may includecircuitry. The physical device may be, for example, a field-programmablegate array, application specific integrated circuit, programmableprocessor, microcontroller, digital signal processor, or other hardwareprocessor. The physical device may be adapted to provide thefunctionality of the virtual blob generator (110) described throughoutthis application.

In one or more embodiments of the invention, the virtual blob generator(110) is implemented as computer instructions, e.g., computer code,stored on a persistent storage that when executed by a processor of edgedevice A (100A) or the DPU (104) causes edge device A (100A) or the DPU(104) to provide the functionality of the virtual blob generator (110)described throughout this application.

In one or more embodiments of the invention, the DPU (104) is one ormore physical devices. The physical device may include circuitry. Thephysical device may be, for example, a field-programmable gate array,application specific integrated circuit, programmable processor,microcontroller, digital signal processor, or other hardware processor.The physical device may be adapted to provide the functionality of theDPU (104) described throughout this application.

In one or more embodiments of the invention, the DPU (104) isimplemented as computer instructions, e.g., computer code, stored on apersistent storage that when executed by a processor of edge device A(100A) causes edge device A (100A) to provide the functionality of theDPU (104) described throughout this application.

In one or more embodiments of the invention, the edge storage (112)stores data. The data stored in edge storage (112) may include videodata and video metadata (both discussed below, see FIG. 2B). The edgestorage (112) may store other and/or additional data without departingfrom the invention. The edge storage (112) may include edge persistentstorage (114) and edge volatile storage (116). The edge storage (112)may include additional, fewer, and/or different components withoutdeparting from the invention. Each of the aforementioned components isdiscussed below.

In one or more embodiments of the invention, edge persistent storage(114) stores video metadata. For additional information regarding videometadata, refer to FIG. 2A. The edge persistent storage (114) may be aform of non-volatile storage. In other words, edge persistent storage(114) may not require constant power to retain data. Edge persistentstorage (114) may store video metadata generated by the DPU (104) andprovide video metadata to the DPU (104). Edge persistent storage (114)may store other and/or additional data without departing from theinvention.

In one or more embodiments of the invention, edge volatile storage (116)stores video data. For additional information regarding video data,refer to FIG. 2B. The edge volatile storage (116) may be a form ofvolatile storage. In other words, the edge volatile storage (116) mayrequire power to retain data. The edge volatile storage (116) may storeand provide data faster than edge persistent storage (114). Edgevolatile storage (116) may store video data obtained from video camerasfor processing or video data obtained from backup storages (120, FIG.1A) to provide to users of the system. Edge volatile storage (116) maystore other and/or additional data without departing from the invention.

Edge storage (112) may be implemented using physical storage devicesand/or logical storage devices. The physical storage devices may includeany combination of hard disk drives, solid state disk drives, tapedrives, random-access memory (RAM), and/or any other physical storagemediums for the storage of data.

The logical storage devices (e.g., virtualized storage) may utilize anyquantity of hardware storage resources of any number of computingdevices for storing data. For example, the edge storage (112) mayutilize portions of any combination of hard disk drives, solid statedisk drives, tape drives, random-access memory (RAM) and/or any otherphysical storage medium of any number of computing devices.

FIG. 1C shows a diagram of a backup storage in accordance with one ormore embodiments of the invention. Backup storage A (120A) may be anembodiment of a backup storage (e.g., 120A, FIG. 1A) discussed above. Asdiscussed above, backup storage A (120A) may include the functionalityto store video data. Backup storage A (120A) may include a backupmanager (122), primary storage (124), secondary storage (126), andarchival storage (128). Backup storage A (120A) may include additional,fewer, and/or different components without departing from the invention.Each of the aforementioned components is discussed below.

In one or more embodiments of the invention, the backup manager (122)includes the functionality to store video data obtained from edgedevices (100, FIG. 1A) in primary storage (124), secondary storage(126), and archival storage (128) and provide video data to edge devices(100, FIG. 1A). The backup manager (122) may also include thefunctionality to de-stage (i.e., move video data from one storage toanother) video data and delete video data. The backup manager (122) mayinclude other and/or additional functionality without departing from theinvention.

In one or more embodiments of the invention, the backup manager (122) isone or more physical devices. The physical device may include circuitry.The physical device may be, for example, a field-programmable gatearray, application specific integrated circuit, programmable processor,microcontroller, digital signal processor, or other hardware processor.The physical device may be adapted to provide the functionality of thebackup manager (122) described throughout this application.

In one or more embodiments of the invention, the backup manager (122) isimplemented as computer instructions, e.g., computer code, stored on apersistent storage that when executed by a processor of backup storage A(120A) causes backup storage A (120A) to provide the functionality ofthe backup manager (122) described throughout this application.

In one or more embodiments of the invention, the primary storage (124)stores primary storage processed video data (132) and the primarystorage raw video data (134). The primary storage (124) may be highperformance storage (e.g., may include fast read/writes speeds) and maybe used for highly relevant video data. Storing video data in primarystorage (124) may be expensive. The primary storage (124) may include ahigher performance than the secondary storage (126) and the archivalstorage (128), and the primary storage (124) may be more expensive thansecondary storage (126) and archival storage (128). Primary storage(124) may be used for short term storage of video data. Primary storage(124) may store other and/or additional data and may include otherand/or additional functionalities without departing from the invention.

In one or more embodiments of the invention, the secondary storage (126)stores secondary storage processed video data (142) and secondarystorage raw video data (144). The secondary storage (126) may be mediumperformance storage (e.g., may include medium read/writes speeds). Thesecondary storage (126) may include a higher performance than thearchival storage (128), but a lower performance than the primary storage(124). The secondary storage (126) may be more expensive than archivalstorage (128) but less expensive than the primary storage (124).Secondary storage (126) may be used for medium term storage of videodata. Secondary storage (126) may store other and/or additional data andmay include other and/or additional functionalities without departingfrom the invention.

In one or more embodiments of the invention, the archival storage (128)stores archival storage processed video data (152) and archival storageraw video data (154). The archival storage (128) may be low performancestorage (e.g., may include slow read/writes speeds) and may be used fornon-highly relevant video data. Storing video data in archival storage(128) may be cheap. The archival storage (128) may include a lowerperformance than the primary storage (124) and the secondary storage(126) and the archival storage (128), but may be cheaper than theprimary storage (124) and the secondary storage (126). Archival storage(128) may be used for long term storage of video data. Archival storage(128) may store other and/or additional data and may include otherand/or additional functionalities without departing from the invention.

In one or more embodiments of the invention, processed video data, e.g.,primary storage processed video data (132), secondary storage processedvideo data (142), and archival storage processed video data (152),includes video data processed by the DPU (104, FIG. 1B). For additionalinformation regarding processed video data, refer to FIG. 1B.

Raw video data, e.g., primary storage raw video data (134), secondarystorage raw video data (144), and archival storage raw video data (154),may include video data not processed by the DPU (104, FIG. 1B). The rawvideo data may not include video metadata associated with the videodata. The raw video data may only include video data chunks.

The primary storage (124), secondary storage (126), and archival storage(128) may be implemented using physical storage devices and/or logicalstorage devices. The physical storage devices may include anycombination of hard disk drives, solid state disk drives, tape drives,and/or any other physical storage mediums for the storage of data.

The logical storage devices (e.g., virtualized storage) may utilize anyquantity of hardware storage resources of any number of computingdevices for storing data. For example, the primary storage (124),secondary storage (126), and archival storage (128) may utilize portionsof any combination of hard disk drives, solid state disk drives, tapedrives, and/or any other physical storage medium of any number ofcomputing devices.

FIG. 2A shows a diagram of video metadata (200) in accordance with oneor more embodiments of the invention. As discussed above, video metadata(200) may include information regarding video data obtained from videocameras and/or backup storages (120, FIG. 1A). The video metadata (200)may include one or more video stream metadata entries, e.g., videostream A metadata entry (200A), video stream B metadata entry (200B),video stream N metadata entry (200N). Each video stream metadata entry(e.g., 200A) may include one or more data structures that includeinformation regarding the video data associated with the video stream.Each video stream metadata entry (e.g., 200A) may include storage tiermetadata (202), authentication and authorization (AA) metadata (204),compliance metadata (206), retention and staging metadata (208),indexing metadata (210), and contextual metadata (212). Each of thevideo stream metadata entries may include other and/or additional datastructures without departing from the invention. Each of theaforementioned data structures is discussed below.

Storage tier metadata (202) may be one or more data structures generatedby the DPU (104, FIG. 1B) during a storage tier operation. The storagetier metadata (202) may include storage tier identifiers. The storagetier identifiers may be unique, global bit strings that are associatedwith a type of storage. One storage tier identifier may be associatedwith primary storage (e.g., 124, FIG. 1C), one storage tier identifiermay be associated with secondary storage (e.g., 126, FIG. 1C), and onestorage tier identifier may be associated with archival storage (e.g.,128, FIG. 1C). The storage tier metadata (202) may include the videodata chunk identifiers of each video data chunk associated with thestorage tier metadata. Each video data chunk identifier may beassociated with one of the storage tier identifiers. The DPU (104, FIG.1B) may use the storage tier metadata (202) to efficiently store videodata chunks in backup storages (120, FIG. 1A). Storage tier metadata mayalso include reference counts, which, if a video data chunk is stored inone storage but referenced multiple times, indicates how many references(e.g., pointers) are associated with the video data chunk. Each videodata chunk of a video stream may be associated with similar or differentstorage tier metadata without departing from the invention. The storagetier metadata may include erasure coding and/or replication flags, whichwhen set, instructs the backup storage to perform erasure coding and/orreplication on the video data chunks when stored. Storage tier metadata(202) may include other and/or additional information regarding whichtype of storage video data chunks are stored within and how they arestored without departing from the invention.

AA metadata (204) may be one or more data structures generated by theDPU (104, FIG. 1B) during an authentication and authorization operation.AA metadata (204) may include authentication and authorizationassociated with each video data chunk. The authentication andauthorization information, may include object identifiers, useridentifiers, group identifiers, access types, authorization and otherand/or additional information regarding the authentication andauthorization information associated with video data chunks. The objectidentifiers may be unique, global bit strings associated with a videodata chunk to differentiate a particular video data chunk from othervideo data chunks.

The user identifiers may be unique, global bit strings associated with auser that has permission to access the video data chunk associated withthe user identifiers. The group identifiers may be unique, global bitstrings associated with a group that has permission to access the videodata chunk associated with the user identifiers. The access type mayrefer to the type of access a user may have with a video data chunk. Theaccess type may specify whether a video data chunk is full access orplaced under legal hold and the period of time the video data chunk isunder legal hold. Full access may refer to video data chunk that may beaccessed by a user. Legal hold may refer to a video data chunk that maynot be accessed or modified and/or deleted in any way due to ongoinglitigation associated with the video data chunk. Authorization may referto what access a user is authorized to have with a video data chunk. Theauthorization may specify whether a user has read only access, read andwrite access, or another type of access without departing from theinvention. AA metadata (204) may be used by the DPU (104, FIG. 1B) tosecure the video data chunks.

Compliance metadata (206) may be one or more data structures generatedby the DPU (104, FIG. 1B) during a compliance operation. The compliancemetadata (206) may specify compliance requirements associated with avideo data chunk. The compliance requirements may specify geographiclocation requirements, industry requirements, organization requirements,policy requirements, and/or other and/or additional compliancerequirements associated with a video data chunk without departing fromthe invention. The compliance metadata may be associated with any numberof video data chunks of a video stream, where each video data chunk ofthe video stream may be associated with similar or different compliancemetadata without departing from the invention. The compliance metadata(206) may be used by the DPU (140, FIG. 1B) and backup storages (120,FIG. 1A) to store video data chunks in storages that meet compliancerequirements.

Retention and staging metadata (208) may be one or more data structuresgenerated by the DPU (104, FIG. 1B) during a retention and stagingoperation. Retention and staging metadata (208) may include retentionand staging information associated with each video data chunk. Theretention information may specify a long term retention period, or anamount of time the video data chunk may not be deleted from the backupstorage (e.g., 120A, FIG. 1A). The staging information may specify thestorage type(s) (e.g., primary storage, secondary storage, and/orarchival storage) a video data chunk is to be stored into and aretention period each storage type, or an amount of time the video datachunk is to be stored in each storage type. The retention and stagingmetadata may also include the storage locations of each video data chunkin the backup storages. The DPU (104, FIG. 1B) may use the retention andstaging metadata (208) to store video data chunks in appropriate storagetypes and track the storage locations of video data chunks as de-stagingoccurs by the backup storages (120A, FIG. 1A). The backup storages(120A, FIG. 1A) may using the retention and staging metadata (208) tode-stage video data chunks to different storage types.

Indexing metadata (210) may be one or more data structures generated bythe DPU (104, FIG. 1B) during an indexing operation. The indexingmetadata (210) may include indexing information associated with eachvideo data chunk. The indexing information may include video data chunkidentifiers, stream identifiers, start times, end times, indexingattributes, and a reference count. The video data chunk identifiers maybe unique, global bit strings associated with video data chunks todifferentiate video data chunks from other video data chunks. The streamidentifiers may be unique, global bit strings associated with videostreams (i.e., collection of video data chunks) to differentiate videostreams from other video streams. Start times may represent timestampsin the video stream at which video data chunks start. Stop times mayrepresent timestamps in the video stream at which video data chunks end.Indexing attributes may specify people, objects, scenes, or any otherrelevant portion or subject of the video stream without departing fromthe invention. Reference counts may specify how many times a video datachunk is stored in the backup storages (120, FIG. 1A). The indexingmetadata may include other and/or additional information regarding thevideo data chunks without departing from the invention. The indexingmetadata (210) may be used by the DPU (104, FIG. 1B) to search for videodata chunks stored in backup storages (120, FIG. 1A).

Contextual metadata (212) may be one or more data structures generatedby the DPU (104, FIG. 1B) during an contextual operation. Contextualmetadata (212) may include contextual attributes associated with thevideo data chunks. The contextual attributes may include behavior and/orlanguage tags. Behavior tags may indicate the actions and or emotionsexhibited by a person in a video. Language tags may indicate what anindividual said in a video. The contextual metadata (212) may includeother and/or additional information associated with video data chunkswithout departing from the invention.

While the data structures (e.g., 202, 204, 206, 208, 210, 212) areillustrated as separate data structures and have been discussed asincluding a limited amount of specific information, any of theaforementioned data structures may be divided into any number of datastructures, combined with any number of other data structures, and mayinclude additional, less, and/or different information without departingfrom the invention. Any of the aforementioned data structures may bestored in different locations (e.g., in persistent storage of othercomputing devices) and/or spanned across any number of computing deviceswithout departing from the invention. Any of the aforementioned datastructures may be implemented using, for example, lists, tables, linkedlists, databases, and/or other types of data structures.

FIG. 2B shows a diagram of processed video data in accordance with oneor more embodiments of the invention. The processed video data (260) maybe an embodiment of processed video (e.g., 132, 142, 152, FIG. 1C) datadiscussed above. As discussed above, the processed video data (260) mayinclude video data processed by the DPU (104, FIG. 1B). The processedvideo data (260) may include one or more video data chunks, e.g., videodata chunk A (262A) and video data chunk N (262N), and one or more videodata chunk metadata, e.g., video data chunks A metadata (264A) and videodata chunk N metadata (264N). The processed video data (260) may includeother and/or additional components without departing from the invention.Each of the aforementioned components of the processed video data isdiscussed below.

A video data chunk (262A, 262N) may be a data structure that includes aportion of video data that was obtained from a video camera. The videodata chunks (262A, 262N) may be unique video data chunks that wereprocessed by a DPU (e.g., 104, FIG. 1B) of the system. Each of the videodata chunks (262A, 262N) may be used by a DPU (e.g., 104, FIG. 1B) (oranother component of the system) to reconstruct video data (e.g., avideo file) that was processed and stored in the system.

Video data chunk metadata (264A, 264N) may be a data structure thatincludes information associated with a video data chunk (e.g., 262A,262N). Video data chunk metadata may include all, or a portion of thevideo metadata (discussed above) associated with a video data chunk(e.g., 262A, 262N). For additional information regarding video metadata,refer to FIG. 2A.

FIG. 3A shows a flowchart of a method for performing an indexingoperation in accordance with one or more embodiments of the invention.The method shown in FIG. 3A may be performed by, for example, a DPU(e.g., 104, FIG. 1B) of an edge device. Other components of the systemillustrated in FIG. 1A may perform all, or a portion, of the method ofFIG. 3A without departing from the invention. While various steps in theflowchart are presented and described sequentially, one of ordinaryskill in the relevant art will appreciate that some or all of the stepsmay be executed in different orders, may be combined or omitted, andsome or all of the steps may be executed in parallel.

In step 300, video data is obtained. In one or more embodiments of theinvention, the video data is obtained from a video camera. The videocamera may send a message to the peripheral interface of the edge devicethrough the local connection. The message may include a video file. Thevideo file may include video data. The video file may include otherand/or additional data without departing from the invention. Theperipheral interface may provide the video data to the DPU. The videodata may be obtained via other and/or additional methods withoutdeparting from the invention.

In another embodiment of the invention, a video camera streams the videodata to the peripheral interface of the edge device. In other words, thevideo camera transmits the video data through the local connection tothe peripheral device as a steady, continuous flow. The peripheraldevice may provide the video data to the DPU. The video data may beobtained via other and/or additional methods without departing from theinvention.

In another embodiment of the invention, the DPU obtains a request toprocess video data from a user. The request may specify raw video datastored in a backup storage. As discussed above, raw video data may bevideo data that has not been processed by a DPU. The DPU may send amessage to the backup storage associated with the raw video data througha non-local connection. The message may include a request to obtain rawvideo data. In response to obtaining the request, the backup storage maysend the raw video data to the DPU. The video data may be obtained viaother and/or additional methods without departing from the invention.

In step 302, the video data is processed to obtain video data chunks andindexing attributes. In one or more embodiments of the invention, theDPU applies data analytics model(s) (discussed above) of the videoprocessing engine to the video data. The data analytics model(s) mayidentify one or more indexing attributes associated with the video data.The data analytics model(s) may break up the video data into video datachunks associated with the one or more indexing attributes. Eachindexing attribute may be associated with one or more video data chunks.The data analytics model(s) may identify any number of indexingattributes and divide the video data into any number of video datachunks without departing from the invention. The video data may beprocessed to obtain video data chunks and indexing attributes via otherand/or additional methods without departing from the invention.

For example, video data obtained from a checkout security camera. Thevideo data may include the checkouts of two different people. The DPUmay apply the data analytics model(s) to the video data. The dataanalytics model(s) may identify a first person and a second person inthe video data. The data analytics model(s) may then divide the videodata into two video data chunks, with the first video data chunkassociated with the first person and the second video data chunkassociated with the second person.

In step 304, indexing metadata is generated based on the video datachunks and the indexing attributes. In one or more embodiments of theinvention, the DPU generates indexing metadata using the video datachunks and the indexing attributes. The DPU may generate or update avideo stream metadata entry. The DPU may include indexing metadata inthe video stream metadata entry. The DPU may generate and include astream identifier associated with the video data chunks in the indexingmetadata. The DPU may generate and include a video data chunk identifierassociated with each video data chunk in the indexing metadata. The DPUmay generate and include start times and stop times of each video datachunk in the indexing metadata. The DPU may generate and include subjectidentifiers associated with each indexing attribute in the indexingmetadata. The DPU may generate and include other and/or additionalinformation regarding the video data chunks and/or the indexingattributes in the indexing metadata without departing from theinvention. The indexing metadata may be generated based on the videodata chunks and the indexing attributes via other and/or additionalmethods without departing from the invention.

In step 306, the indexing metadata is associated with the video datachunks. In one or more embodiments of the invention, the DPU updates theindexing metadata of the video stream metadata entry associated with thevideo data to associate the indexing metadata with the video datachunks. The DPU may associate the video data chunk identifiersassociated with each video data chunk with the information included inthe indexing metadata associated with the video data chunk. For example,the DPU may relate the video data chunk identifier associated with afirst video data chunk with the indexing attribute included in the firstvideo data chunk, the start time of the first video data chunk, and theend time of the first video data chunk. The indexing metadata may beassociated with the video data chunks via other and/or additionalmethods without departing from the invention.

In step 308, the indexing metadata and the video data chunks are stored.In one or more embodiments of the invention, the DPU stores the indexingmetadata in the edge persistent storage of the edge device and the videodata chunks in a backup storage. The DPU may also generate copies ofall, or a portion, of the indexing metadata and include the copies withthe video data chunks stored in the backup storage. The DPU may send amessage to the backup storage through the non-local connection. Themessage may include the video data chunks, the copies of all, or aportion, of the indexing metadata, and a request to store the video datachunks and the copies of the indexing metadata in the backup storage. Inresponse to obtaining the message, the backup storage stores the videodata chunks and the copies of indexing metadata in persistent storage.The indexing metadata and the video data chunks may be stored via otherand/or additional methods without departing from the invention.

The method may end following step 308.

FIG. 3B shows a diagram of a first example in accordance with one ormore embodiments of the invention. The example depicted in FIG. 3B maydepict an indexing operation. The example is not intended to limit thescope of the invention. The example system depicted in FIG. 3B mayinclude fewer components than the systems depicted in FIGS. 1A-1C forthe sake of brevity.

Turning to the example, consider a scenario in which a video camera (notshown) provides video data to an edge device (300). The edge device(300) includes a DPU (302) and edge persistent storage (310).

Initially, the DPU (302) obtains video data (304) from a video camera(not shown) [1]. After obtaining the video data (304), the DPU (302)applies the video data to the data analytics models of the videoprocessing engine (not shown) of the DPU (302) to generate video datachunks (306) and indexing attributes (308) [2]. The video data chunks(306) includes video data chunk A (306A) and video data chunk B (306B).The indexing attributes (308) include person A (308A) and person B(308B). Following the generation of the video data chunks (306) and theindexing attributes (308), the DPU (304) generates indexing metadata(312) based on the video data chunks (306) and the indexing attributes(308) [3]. The indexing metadata (312) includes stream ID A (314A) andinformation associated with both video data chunks (306A, 306B). Theinformation associated with video data chunk A (306A) includes videodata chunk ID A (316A), start time A (318A), and end time A (320A). Theinformation associated with video data chunk B (306B) includes videodata chunk ID B (316B), start time B (318B), and end time B (320B).

Then, the DPU (304) associates the indexing metadata (312) with thevideo data chunks (306) by associating the video data chunk IDs (316A,316B) with the indexing attributes (308A, 308B) with which they areassociated [4]. In this example, person A (308A) appears in video datachunk A (306A) and is associated with video data chunk ID A (316A), andperson B (308B) appears in video data chunk B (306B) and is associatedin video data chunk ID B (316B). Finally, the DPU (304) sends the videodata chunks (306A, 306B) and copies of portions of the indexing metadata(312) to the backup storage (330), where video data chunks (306A, 306B)and the copies of portions of the indexing metadata (312) are stored inprimary storage (332) as processed primary storage video data (334) [5].The processed primary storage video data (334) includes video data chunkA (306A), the copies of portions of the indexing metadata associatedwith video data chunk A (306A) (i.e., video data chunk ID A (316A),start time A (318A), and end time A (320A)), video data chunks B (306B),and the copies of portions of indexing metadata associated with videodata chunk B (306B) (i.e., video data chunk ID B (316B), start time B(318B), and end time B (320B)).

FIG. 4A shows a flowchart of a method for performing a contextualoperation in accordance with one or more embodiments of the invention.The method shown in FIG. 4A may be performed by, for example, a DPU(e.g., 104, FIG. 1B) of an edge device. Other components of the systemillustrated in FIG. 1A may perform all, or a portion, of the method ofFIG. 4A without departing from the invention. While various steps in theflowchart are presented and described sequentially, one of ordinaryskill in the relevant art will appreciate that some or all of the stepsmay be executed in different orders, may be combined or omitted, andsome or all of the steps may be executed in parallel.

In step 400, video data is obtained. In one or more embodiments of theinvention, the video data is obtained from a video camera. The videocamera may send a message to the peripheral interface of the edge devicethrough the local connection. The message may include a video file. Thevideo file may include video data. The video file may include otherand/or additional data without departing from the invention. Theperipheral interface may provide the video data to the DPU. The videodata may be obtained via other and/or additional methods withoutdeparting from the invention.

In another embodiment of the invention, a video camera streams the videodata to the peripheral interface of the edge device. In other words, thevideo camera transmits the video data through the local connection tothe peripheral device as a steady, continuous flow. The peripheraldevice may provide the video data to the DPU. The video data may beobtained via other and/or additional methods without departing from theinvention.

In another embodiment of the invention, the DPU obtains a request toprocess video data from a user. The request may specify raw video datastored in a backup storage. As discussed above, raw video data may bevideo data that has not been processed by a DPU. The DPU may send amessage to the backup storage associated with the raw video data througha non-local connection. The message may include a request to obtain rawvideo data. In response to obtaining the request, the backup storage maysend the raw video data to the DPU. The video data may be obtained viaother and/or additional methods without departing from the invention.

In step 402, the video data is processed to obtain video data chunks andindexing attributes. In one or more embodiments of the invention, theDPU applies data analytics model(s) (discussed above) of the videoprocessing engine to the video data. The data analytics model(s) mayidentify one or more indexing attributes associated with the video data.The data analytics model(s) may break up the video data into video datachunks associated with the one or more indexing attributes. Eachindexing attribute may be associated with one or more video data chunks.The data analytics model(s) may identify any number of indexingattributes and divide the video data into any number of video datachunks without departing from the invention. The video data may beprocessed to obtain video data chunks and indexing attributes via otherand/or additional methods without departing from the invention.

For example, video data obtained from a checkout security camera. Thevideo data may include the checkouts of two different people. The DPUmay apply the data analytics model(s) to the video data. The dataanalytics model(s) may identify a first person and a second person inthe video data. The data analytics model(s) may then divide the videodata into two video data chunks, with the first video data chunkassociated with the first person and the second video data chunkassociated with the second person.

In step 404, indexing metadata is generated based on the video datachunks and the indexing attributes. In one or more embodiments of theinvention, the DPU generates indexing metadata using the video datachunks and the indexing attributes. The DPU may generate or update avideo stream metadata entry. The DPU may include indexing metadata inthe video stream metadata entry. The DPU may generate and include astream identifier associated with the video data chunks in the indexingmetadata. The DPU may generate and include a video data chunk identifierassociated with each video data chunk in the indexing metadata. The DPUmay generate and include start times and stop times of each video datachunk in the indexing metadata. The DPU may generate and include subjectidentifiers associated with each indexing attribute in the indexingmetadata. The DPU may generate and include other and/or additionalinformation regarding the video data chunks and/or the indexingattributes in the indexing metadata without departing from theinvention. The indexing metadata may be generated based on the videodata chunks and the indexing attributes via other and/or additionalmethods without departing from the invention.

In step 406, the video data chunks and the indexing attributes areprocessed to generate contextual attributes. In one or more embodimentsof the invention, the DPU applies context generation model(s) (discussedabove) of the context generator to the video data chunks and theindexing attributes. The context generation model(s) may identify anynumber of contextual attributes associated with each indexing attribute.Each contextual attribute may be associated with a video data chunk. Thevideo data chunks and the indexing attributes may be processed togenerate contextual attributes via other and/or additional methodswithout departing from the invention.

Continuing with the example discussed in step 402, the DPU may apply thecontext generation model(s) to the two video data chunks and the twoindexing attributes (the two people checking out). The contextgeneration model(s) may identify that the first person is nervous andmade a pretense, and may therefore generate two contextual attributes,nervous and pretense, associated with the first indexing attribute, thefirst person. The context generation model(s) may identify that thesecond person is happy and confident, and may therefore generate twocontextual attributes, happy and confident, associated with the secondperson.

In step 408, contextual metadata is generated based on the video datachunks and the contextual attributes. In one or more embodiments of theinvention, the DPU generates the contextual metadata using thecontextual attributes and the video data chunks. The DPU may update thevideo stream metadata entry associated with the video data chunks. TheDPU may include contextual metadata in the video stream metadata entry.The DPU may generate and include context identifiers associated with thecontextual attributes in the contextual metadata. The DPU may generateand include other and/or additional information regarding the contextualattributes in the contextual metadata without departing from theinvention. Contextual metadata may be generated based on the video datachunks and the contextual attributes via other and/or additional methodswithout departing from the invention.

In step 410, the contextual metadata and indexing metadata areassociated with the video data chunks. In one or more embodiments of theinvention, the DPU updates the indexing metadata of the video streammetadata entry associated with the video data to associate the indexingmetadata with the video data chunks. The DPU may associate the videodata chunk identifiers associated with each video data chunk with theinformation included in the indexing metadata associated with the videodata chunk. For example, the DPU may relate the video data chunkidentifier associated with a first video data chunk with the indexingattribute included in the first video data chunk, the start time of thefirst video data chunk, and the end time of the first video data chunk.The indexing metadata may be associated with the video data chunks viaother and/or additional methods without departing from the invention.

In one or more embodiments of the invention, the DPU updates thecontextual metadata of the video stream metadata entry associated withthe video data chunks to associate the contextual metadata with thevideo data chunks. The DPU may associate the video data chunkidentifiers associated with each video data chunk with the contextidentifiers associated with the video data chunk. The contextualmetadata may be associated with the video data chunks via other and/oradditional methods without departing from the invention.

In step 412, the indexing metadata, contextual metadata, and the videodata chunks are stored. In one or more embodiments of the invention, theDPU stores the indexing metadata and contextual metadata in the edgepersistent storage of the edge device and the video data chunks in abackup storage. The DPU may also generate copies of all, or a portion,of the indexing metadata and the contextual metadata and include thecopies with the video data chunks stored in the backup storage. The DPUmay send a message to the backup storage through the non-localconnection. The message may include the video data chunks, the copies ofall, or a portion, of the indexing metadata and contextual metadata, anda request to store the video data chunks and the copies of the indexingmetadata and contextual metadata in the backup storage. In response toobtaining the message, the backup storage may store the video datachunks and the copies of indexing metadata and contextual metadata inpersistent storage. The indexing metadata, contextual metadata, and thevideo data chunks may be stored via other and/or additional methodswithout departing from the invention.

The method may end following step 412.

FIG. 4B shows a diagram of a second example in accordance with one ormore embodiments of the invention. The example depicted in FIG. 4B maydepict a contextual operation. The example is not intended to limit thescope of the invention. The example system depicted in FIG. 4B mayinclude fewer components than the systems depicted in FIGS. 1A-1C forthe sake of brevity.

Turning to the example, consider a scenario in which a video camera (notshown) provides video data to an edge device (400). The edge device(400) includes a DPU (402) and edge persistent storage (404).

Initially, the DPU (402) obtains video data (408) from a video camera(not shown) [1]. After obtaining the video data (408), the DPU (402)applies the video data to the data analytics model(s) of the videoprocessing engine (not shown) of the DPU (402) to generate video datachunks (410) and indexing attributes (412) [2]. The video data chunks(410) includes video data chunk A (410A) and video data chunk B (410B).The indexing attributes (412) include person A (412A) and person B(412B). Following the generation of the video data chunks (410) and theindexing attributes (412), the DPU (402) generates indexing metadata(416) based on the video data chunks (410) and the indexing attributes(412) [3]. The indexing metadata (416) includes stream ID A (418A) andinformation associated with both video data chunks (410A, 410B). Theinformation associated with video data chunk A (410A) includes videodata chunk ID A (420A), start time A (422A), and end time A (424A). Theinformation associated with video data chunk B (410B) includes videodata chunk ID B (420B), start time B (422B), and end time B (424B).

After the generation of the indexing metadata (416), the DPU (402)applies the context generation models of the context generator (notshown) to the video data chunks (410A, 410B) and the indexing attributes(412A, 412B) to generate the contextual attributes (414) [4]. Thecontext generation model(s) determine that person A (412A) appears happyand person B (412B) appears nervous, and therefore, generates thecontextual attributes (414), which include happy (414A) and nervous(414B). The DPU (402) then generates contextual metadata (426) using thecontextual attributes (414), the indexing attributes (412) and the videodata chunks (410) [5]. The contextual metadata (426) includes theindexing attributes (412) associated with their corresponding contextualattributes (414). Accordingly, person A (412A) is associated with happy(414A) and person B (412B) is associated with nervous (414B).

Then, the DPU (402) associates the indexing metadata (416) and thecontextual metadata (426) with the video data chunks (410A, 410B) byassociating the video data chunk IDs (420A, 420B) with the indexingattributes (412A, 412B) with which they are associated [6]. In thisexample, person A (412A) appears in video data chunk A (410A) and isassociated with video data chunks ID A (420A), and person B (412B)appears in video data chunk B (410B) and is associated in video datachunk ID B (420B). Finally, the DPU (402) sends the video data chunks(410A, 410B) and copies of portions of the indexing metadata (416) tothe backup storage (430), where video data chunks (410A, 410B) and thecopies of portions of the indexing metadata (416) are stored in primarystorage (432) as processed primary storage video data (434), and theindexing metadata (416) and contextual metadata (426) are stored in edgepersistent storage (404) [7]. The processed primary storage video data(434) includes video data chunk A (410A), the copies of portions of theindexing metadata associated with video data chunk A (410A) (i.e., videodata chunk ID A (420A), start time A (422A), and end time A (424A)),video data chunk B (410B), and the copies of portions of indexingmetadata associated with video data chunk B (410B) (i.e., video datachunk ID B (420B), start time B (422B), and end time B (424B)).

FIG. 5A shows a flowchart of a method for performing a storage tieroperation in accordance with one or more embodiments of the invention.The method shown in FIG. 5A may be performed by, for example, a DPU(e.g., 104, FIG. 1B) of an edge device. Other components of the systemillustrated in FIG. 1A may perform all, or a portion, of the method ofFIG. 5A without departing from the invention. While various steps in theflowchart are presented and described sequentially, one of ordinaryskill in the relevant art will appreciate that some or all of the stepsmay be executed in different orders, may be combined or omitted, andsome or all of the steps may be executed in parallel.

In step 500, video data is obtained. In one or more embodiments of theinvention, the video data is obtained from a video camera. The videocamera may send a message to the peripheral interface of the edge devicethrough the local connection. The message may include a video file. Thevideo file may include video data. The video file may include otherand/or additional data without departing from the invention. Theperipheral interface may provide the video data to the DPU. The videodata may be obtained via other and/or additional methods withoutdeparting from the invention.

In another embodiment of the invention, a video camera streams the videodata to the peripheral interface of the edge device. In other words, thevideo camera transmits the video data through the local connection tothe peripheral device as a steady, continuous flow. The peripheraldevice may provide the video data to the DPU. The video data may beobtained via other and/or additional methods without departing from theinvention.

In step 502, the video data is processed to obtain video data chunks andvideo processing engine outcomes. In one or more embodiments of theinvention, the DPU applies data analytics model(s) (discussed above) ofthe video processing engine to the video data. The data analyticsmodel(s) may generate one or more video processing engine outcomesassociated with the video data. The video processing engine outcomes mayinclude, for example, facial recognition, fraud detection, and otherand/or additional video processing engine outcomes as discussed above.The data analytics model(s) may break up the video data into video datachunks associated with the one or more video processing engine outcome.Each video processing engine outcome may be associated with one or morevideo data chunks and each video data chunk may be associated with oneor more video processing engine outcomes. The data analytics model(s)may generate any number of video processing engine outcomes and dividethe video data into any number of video data chunks without departingfrom the invention. The video data may be processed to obtain video datachunks and video processing engine outcomes via other and/or additionalmethods without departing from the invention.

In step 504, storage tier metadata is generated based on the video datachunks and the video processing engine outcomes. In one or moreembodiments of the invention, the DPU generates storage tier metadatausing the video data chunks and the video processing engine outcomes.The DPU may generate or update a video stream metadata entry. The DPUmay include storage tier metadata in the video stream metadata entry.The DPU may generate and include storage tier identifiers associatedwith the video data chunks in the storage tier metadata. The DPU mayinclude a storage tier assignment policies obtained from a user of thesystem. The storage tier assignment policies may include storage tierrequirements for the one or more video processing engine outcomes. Thestorage tier requirements may specify a storage type (e.g., primarystorage, secondary storage, archival storage) of the backup storage tostore a video data chunk associated with a given video processing engineoutcome. The DPU may compare the video processing engine outcomesassociated with the video data chunks with the video processing engineoutcomes included in the storage tier assignment policies and includestorage tier identifiers associated with storage types in the storagetier metadata based on the comparisons. The storage tier metadata may begenerated based on the video data chunks and the video processing engineoutcomes via other and/or additional methods without departing from theinvention.

In step 506, the storage tier metadata is associated with the video datachunks. In one or more embodiments of the invention, the DPU updates thevideo stream metadata entry associated with the video data chunks toassociate the storage tier metadata with the video data chunks. The DPUmay associate the video data chunk identifiers associated with eachvideo data chunk with each storage tier identifier included in thestorage tier metadata. For example, the DPU may associate the video datachunk identifier associated with a first video data chunk with thestorage tier identifier associated with the first video data chunk. Thestorage tier metadata may be associated with the video data chunks viaother and/or additional methods without departing from the invention.

In step 508, the storage tier metadata and video data chunks are storedin appropriate storage based on the storage tier metadata. In one ormore embodiments of the invention, the DPU stores the storage tiermetadata in the edge persistent storage of the edge device and the videodata chunks in a backup storage. The DPU may also generate copies of thestorage tier metadata and include the copies with the video data chunksstored in the backup storage. The DPU may send a message to the backupstorage through the non-local connection. The message may include thevideo data chunks, the copies of the storage tier metadata, and arequest to store the video data chunks, and the copies of the storagetier metadata in the appropriate storages of the backup storage. Inresponse to obtaining the message, the backup storage may store each ofthe video data chunks and the copies of storage tier metadata associatedwith each video data chunk in the appropriate storage based on thestorage tier metadata. The storage tier metadata and the video datachunks may be stored in appropriate storages based on the storage tiermetadata via other and/or additional methods without departing from theinvention.

The method may end following step 508.

FIG. 5B shows a diagram of a third example in accordance with one ormore embodiments of the invention. The example depicted in FIG. 5B maydepict a storage tier operation. The example is not intended to limitthe scope of the invention. The example system depicted in FIG. 5B mayinclude fewer components than the systems depicted in FIGS. 1A-1C forthe sake of brevity.

Turning to the example, consider a scenario in which a video camera (notshown) provides video data to an edge device (500). The edge device(500) includes a DPU (502) and edge persistent storage (504).

Initially, the DPU (502) obtains video data (506) from a video camera(not shown) [1]. After obtaining the video data (506), the DPU (502)applies the video data to the data analytics models of the videoprocessing engine (not shown) of the DPU (502) to generate video datachunks (508) and video processing engine outcomes (510) [2]. The videodata chunks (508) includes video data chunk A (508A) and video datachunk B (508B). The video processing engine outcomes (510) include frauddetection (510A) and facial recognition (510B). Following the generationof the video data chunks (508) and the video processing engine outcomes(510), the DPU (502) generates indexing metadata (512) and storage tiermetadata (522) based on the video data chunks (506) and the videoprocessing engine outcomes (510) [3]. The indexing metadata (512)includes stream ID A (514A) and information associated with both videodata chunks (508A, 508B). The information associated with video datachunk A (508A) includes video data chunk ID A (516A), start time A(518A), and end time A (520A). The information associated with videodata chunk B (508B) includes video data chunk ID B (516B), start time B(518B), and end time B (520B). The storage tier metadata (522) includesstorage tier metadata A (522A) and storage tier metadata B (522B).Storage tier metadata A (522A) specifies that fraud detection (510A) isto be stored in primary storage (532), and storage tier metadata B(522B) specifies that facial recognition (510B) is to be stored inarchival storage (534).

Then, the DPU (502) associates the indexing metadata (512) and thestorage tier metadata (522) with the video data chunks (508) byassociating the video data chunk IDs (516A, 516B) with each storagemetadata (522A, 522B) [4]. In this example, fraud detection (510A)occurs in video data chunk A (508A) and is associated with video datachunk ID A (516A), and facial recognition (510B) occurs in video datachunk B (508B) and is associated in video data chunk ID B (516B).Finally, the DPU (502) sends the video data chunks (508A, 508B) andcopies of portions of the indexing metadata (512) and storage tiermetadata (522) to the backup storage (530). Based on storage tiermetadata A (522A), video data chunk A (508A) and indexing metadataassociated with video data chunk A (508A) are stored in primary storage(532) as processed primary storage video data (536), and based onstorage tier metadata B (522B), video data chunk B (508B) and indexingmetadata (512) associated with video data chunk B (508B) are stored inarchival storage (534) as processed archival storage video data (538)[5]. The processed primary storage video data (536) includes video datachunk A (508A) and the copies of portions of the indexing metadataassociated with video data chunk A (508A) (i.e., video data chunk ID A(516A), start time A (518A), and end time A (520A)). The processedarchival storage video data (538) includes video data chunk B (508B) andthe copies of portions of indexing metadata associated with video datachunk B (506B) (i.e., video data chunk ID B (516B), start time B (518B),and end time B (520B)).

FIG. 6A shows a flowchart of a method for performing a complianceoperation in accordance with one or more embodiments of the invention.The method shown in FIG. 6A may be performed by, for example, a DPU(e.g., 104, FIG. 1B) of an edge device. Other components of the systemillustrated in FIG. 1A may perform all, or a portion, of the method ofFIG. 6A without departing from the invention. While various steps in theflowchart are presented and described sequentially, one of ordinaryskill in the relevant art will appreciate that some or all of the stepsmay be executed in different orders, may be combined or omitted, andsome or all of the steps may be executed in parallel.

In step 600, video data is obtained. In one or more embodiments of theinvention, the video data is obtained from a video camera. The videocamera may send a message to the peripheral interface of the edge devicethrough the local connection. The message may include a video file. Thevideo file may include video data. The video file may include otherand/or additional data without departing from the invention. Theperipheral interface may provide the video data to the DPU. The videodata may be obtained via other and/or additional methods withoutdeparting from the invention.

In another embodiment of the invention, a video camera streams the videodata to the peripheral interface of the edge device. In other words, thevideo camera transmits the video data through the local connection tothe peripheral device as a steady, continuous flow. The peripheraldevice may provide the video data to the DPU. The video data may beobtained via other and/or additional methods without departing from theinvention.

In step 602, the video data is processed to obtain video data chunks andvideo processing engine outcomes. In one or more embodiments of theinvention, the DPU applies data analytics model(s) (discussed above) ofthe video processing engine to the video data. The data analyticsmodel(s) may generate one or more video processing engine outcomesassociated with the video data. The video processing engine outcomes mayinclude, for example, facial recognition, fraud detection, and otherand/or additional video processing engine outcomes as discussed above.The data analytics model(s) may break up the video data into video datachunks associated with the one or more video processing engine outcome.Each video processing engine outcome may be associated with one or morevideo data chunks and each video data chunk may be associated with oneor more video processing engine outcomes. The data analytics model(s)may generate any number of video processing engine outcomes and dividethe video data into any number of video data chunks without departingfrom the invention. The video data may be processed to obtain video datachunks and video processing engine outcomes via other and/or additionalmethods without departing from the invention.

In step 604, compliance metadata is generated based on the video datachunks and the video processing engine outcomes. In one or moreembodiments of the invention, the DPU generates compliance metadatausing the video data chunks and the video processing engine outcomes.The DPU may generate or update a video stream metadata entry. The DPUmay include compliance metadata in the video stream metadata entry. TheDPU may generate and include compliance information (discussed above)associated with the video data chunks in the compliance metadata. TheDPU may include compliance policies obtained from a user of the system.The compliance policies may include compliance requirements for thevideo data chunks associated with the one or more video processingengine outcomes and the video processing engine outcomes associated witheach compliance requirement. The compliance requirements may specify ageographic storage location, organizational requirements, industryrequirements, and/or other and or additional types of compliancerequirements without departing from the invention. The DPU may comparethe video processing engine outcomes associated with the video datachunks with the video processing engine outcomes included in thecompliance policies and include compliance information associated withthe compliance requirements in the compliance metadata based on thecomparisons. The compliance metadata may be generated based on the videodata chunks and the video processing engine outcomes via other and/oradditional methods without departing from the invention.

In step 606, the compliance metadata is associated with the video datachunks. In one or more embodiments of the invention, the DPU updates thevideo stream metadata entry associated with the video data chunks toassociate the compliance metadata with the video data chunks. The DPUmay associate the video data chunk identifiers associated with eachvideo data chunk with each compliance requirement included in thecompliance metadata. For example, the DPU may associate the video datachunk identifier associated with a first video data chunk with a firstcompliance requirement associated with the first video data chunk. Thecompliance metadata may be associated with the video data chunks viaother and/or additional methods without departing from the invention.

In step 608, the compliance metadata and video data chunks are stored inappropriate storage based on the compliance metadata. In one or moreembodiments of the invention, the DPU stores the compliance metadata inthe edge persistent storage of the edge device and the video data chunksin a backup storage. The DPU may also generate copies of the compliancemetadata and include the copies with the video data chunks stored in thebackup storage. The DPU may send a message to the backup storage throughthe non-local connection. The message may include the video data chunks,the copies of the compliance metadata, and a request to store the videodata chunks and the copies of the compliance metadata in the appropriatestorages of the backup storage. In response to obtaining the message,the backup storage may store each of the video data chunks and thecopies of compliance metadata associated with each video data chunk inthe appropriate storage based on the compliance metadata. The compliancemetadata and the video data chunks may be stored in appropriate storagesbased on the compliance metadata via other and/or additional methodswithout departing from the invention.

As a result, the compliance metadata may be used by the DPU to verifythat further operations performed on video data chunks are in accordancewith video data compliance requirements specified in the compliancemetadata. For example, retention and staging metadata may specify that avideo data chunk is to be deleted from a backup storage after one year.However, the compliance metadata associated with the video chunk mayspecify a compliance requirement that indicates the video data chunk isnot to be deleted before three years of being stored in the backupstorage. The DPU may check the compliance metadata associated with thevideo data chunk prior to deleting the video data chunk to determinewhether the compliance metadata allows for the deletion of the videodata chunk following a year of being stored in the backup storage, anddetermine not to delete the video data chunk.

Turning to another example, during a long term stitching operation, theDPU may check with the compliance metadata associated with a video datachunk to determine a backup storage to de-stage the video data chunk to.The compliance metadata may indicate that the video data chunk wasgenerated in North America and must be stored in a data center locatedin North America. The DPU may identify two data centers in which thevideo data chunk may be de-staged to, where the first data center is inNorth America and the second is in Asia. The DPU may determine tode-stage the video data chunk to the video data center located in NorthAmerica based on the compliance metadata associated with the video datachunk.

The method may end following step 608.

FIG. 6B shows a diagram of a fourth example in accordance with one ormore embodiments of the invention. The example depicted in FIG. 6B maydepict a compliance operation. The example is not intended to limit thescope of the invention. The example system depicted in FIG. 6B mayinclude fewer components than the systems depicted in FIGS. 1A-1C forthe sake of brevity.

Turning to the example, consider a scenario in which a video camera (notshown) provides video data to an edge device (600). The edge device(600) includes a DPU (602) and edge persistent storage (604).

Initially, the DPU (602) obtains video data (606) from a video camera(not shown) [1]. After obtaining the video data (606), the DPU (602)applies the video data to the data analytics models of the videoprocessing engine (not shown) of the DPU (602) to generate video datachunks (608) and video processing engine outcomes (610) [2]. The videodata chunks (608) includes video data chunk A (608A) and video datachunk B (608B). The video processing engine outcomes (610) include frauddetection (610A) and facial recognition (610B). Following the generationof the video data chunks (608) and the video processing engine outcomes(610), the DPU (602) generates indexing metadata (612) and compliancemetadata (618) based on the video data chunks (606) and the videoprocessing engine outcomes (610) [3]. The indexing metadata (612)includes stream IDA (614A) and information associated with both videodata chunks (608A, 608B). The information associated with video datachunk A (608A) includes video data chunk ID A (616A). The informationassociated with video data chunk B (608B) includes video data chunk ID B(616B). The compliance metadata (618) includes compliance metadata A(618A) and compliance metadata B (618B). Compliance metadata A (618A)includes compliance information associated with video data chunk A(608A). The compliance information specifies that video data chunk A(608A) is to be located in North America, is associated with a USfederal organization, is to follow the FedRAMP policy, and is to includea retention period of ten years. Compliance metadata B (618B) includescompliance information associated with video data chunk B (608B). Thecompliance information specifies that video data chunk B (608B) is to belocated in the European Union, is associated with a retail storeorganization, is associated with the retail payment industry, is tofollow the PCI DSS policy, and is to include a retention period of oneyear.

Then, the DPU (602) associates the indexing metadata (612) and thecompliance metadata (618) with the video data chunks (608) byassociating the video data chunk IDs (616A, 616B) with each compliancemetadata (618A, 618B) [4]. In this example, fraud detection (610A) in aUS federal organization occurs in video data chunk A (608A) and isassociated with video data chunks ID A (616A), and facial recognition(610B) of an EU retail store occurs in video data chunk B (608B) and isassociated in video data chunk ID B (616B). Finally, the DPU (602) sendsthe video data chunks (608A, 608B) and copies of portions of theindexing metadata (612) and compliance metadata (618) to backup storageA (620A) and backup storage B (620B). Based on compliance metadata A(618A), video data chunk A (608A) and indexing metadata associated withvideo data chunk A (608A) are stored in primary storage A (622A) ofbackup storage A (620A) as processed primary storage video data A (624A)because backup storage A (620A) is located in North America andcompliance metadata A (618A) specifies that video data chunk A (608A) isto be stored in North America. Based on compliance metadata B (618B),video data chunk B (608B) and indexing metadata associated with videodata chunk B (608B) are stored in primary storage B (622B) of backupstorage B (620B) as processed primary storage video data B (624B)because backup storage B (620B) is located in the European Union andcompliance metadata B (618B) specifies that video data chunk B (608A) isto be stored in the European Union [5]. The processed primary storagevideo data A (624A) includes video data chunk A (608A) and the copies ofthe indexing metadata associated with video data chunk A (608A) (i.e.,video data chunk ID A (616A)). The processed primary storage video dataB (624B) includes video data chunk B (608B), and the copies of indexingmetadata associated with video data chunk B (608B) (i.e., video datachunk ID B (616B)).

FIG. 7A shows a flowchart of a method for performing an authenticationand authorization operation in accordance with one or more embodimentsof the invention. The method shown in FIG. 7A may be performed by, forexample, a DPU (e.g., 104, FIG. 1B) of an edge device. Other componentsof the system illustrated in FIG. 1A may perform all, or a portion, ofthe method of FIG. 7A without departing from the invention. Whilevarious steps in the flowchart are presented and described sequentially,one of ordinary skill in the relevant art will appreciate that some orall of the steps may be executed in different orders, may be combined oromitted, and some or all of the steps may be executed in parallel.

In step 700, video data is obtained. In one or more embodiments of theinvention, the video data is obtained from a video camera. The videocamera may send a message to the peripheral interface of the edge devicethrough the local connection. The message may include a video file. Thevideo file may include video data. The video file may include otherand/or additional data without departing from the invention. Theperipheral interface may provide the video data to the DPU. The videodata may be obtained via other and/or additional methods withoutdeparting from the invention.

In another embodiment of the invention, a video camera streams the videodata to the peripheral interface of the edge device. In other words, thevideo camera transmits the video data through the local connection tothe peripheral device as a steady, continuous flow. The peripheraldevice may provide the video data to the DPU. The video data may beobtained via other and/or additional methods without departing from theinvention.

In step 702, the video data is processed to obtain video data chunks andvideo processing engine outcomes. In one or more embodiments of theinvention, the DPU applies data analytics model(s) (discussed above) ofthe video processing engine to the video data. The data analyticsmodel(s) may generate one or more video processing engine outcomesassociated with the video data. The video processing engine outcomes mayinclude, for example, facial recognition, fraud detection, and otherand/or additional video processing engine outcomes as discussed above.The data analytics model(s) may break up the video data into video datachunks associated with the one or more video processing engine outcome.Each video processing engine outcome may be associated with one or morevideo data chunks and each video data chunk may be associated with oneor more video processing engine outcomes. The data analytics model(s)may generate any number of video processing engine outcomes and dividethe video data into any number of video data chunks without departingfrom the invention. The video data may be processed to obtain video datachunks and video processing engine outcomes via other and/or additionalmethods without departing from the invention.

In step 704, AA metadata is generated based on the video data chunks andthe video processing engine outcomes. In one or more embodiments of theinvention, the DPU generates compliance metadata using the video datachunks and the video processing engine outcomes. The DPU may generate orupdate a video stream metadata entry. The DPU may include AA metadata inthe video stream metadata entry. The DPU may generate and includeauthentication and authorization information (discussed above)associated with the video data chunks in the AA metadata. The DPU mayinclude authentication and authorization policies obtained from a userof the system. The authentication and authorization policies may includeauthentication and authorization information for the video data chunksassociated with the one or more video processing engine outcomes and thevideo processing engine outcomes associated with each authentication andauthorization information. The authentication and authorizationinformation may specify which users include access to the video datachunks and the type of access associated with each user. The DPU maycompare the video processing engine outcomes associated with the videodata chunks with the video processing engine outcomes included in theauthentication and authorization policies and include authentication andauthorization information in the AA metadata based on the comparisons.The AA metadata may be generated based on the video data chunks and thevideo processing engine outcomes via other and/or additional methodswithout departing from the invention.

Additionally, the DPU may generate AA metadata associated with the videodata chunks based on the video processing engine outcomes. The videoprocessing engine outcomes may be associated with negative connotations.Negative connotations may include any action or characteristic of asubject of video data that may be considered bad, illegal, and/orfraudulent in any way without departing from the invention. The DPU maygenerate AA metadata for video data chunks associated with negativeconnotations. The AA metadata may specify the video data chunksassociated with the negative connotations are placed under legal hold.The AA metadata may be generated based on the video data chunks and thevideo processing engine outcomes via other and/or additional methodswithout departing from the invention.

In step 706, the AA metadata is associated with the video data chunks.In one or more embodiments of the invention, the DPU updates the videostream metadata entry associated with the video data chunks to associatethe AA metadata with the video data chunks. The DPU may associate thevideo data chunk identifiers associated with each video data chunk witheach authentication and authorization information included in the AAmetadata. For example, the DPU may associate the video data chunkidentifier associated with a first video data chunk with a first set ofauthentication and authorization information associated with the firstvideo data chunk. The AA metadata may be associated with the video datachunks via other and/or additional methods without departing from theinvention.

In step 708, the AA metadata and video data chunks are stored instorage. In one or more embodiments of the invention, the DPU stores theAA metadata and in the edge persistent storage of the edge device andthe video data chunks in a backup storage. The DPU may also generatecopies of all, or a portion, of the AA metadata and include the copiesof the AA metadata with the video data chunks stored in the backupstorage. The DPU may send a message to the backup storage through thenon-local connection. The message may include the video data chunks, thecopies of the AA metadata, and a request to store the video data chunksand the copies of AA metadata in the backup storage. In response toobtaining the message, the backup storage may store the video datachunks and the copies of AA metadata and in persistent storage. The AAmetadata and the video data chunks may be stored via other and/oradditional methods without departing from the invention.

As a result, video data chunks stored with AA metadata that indicatesthe video data chunks are under legal hold may not be deleted whileunder legal hold. For example, a video data chunk may be associated withAA metadata that is placed under legal hold. A deletion request may beobtained by the DPU associated with the video data chunk. The DPU maycheck the AA metadata associated with the video data chunk, anddetermine to reject the deletion request because the AA metadataindicates that the video data chunk is under legal hold. If the AAmetadata indicates that video data chunks are not under legal hold, theDPU may perform any operation on the video data chunks (e.g., delete thevideo data chunks) without the AA metadata associated with the videodata chunks.

The method may end following step 708.

FIG. 7B shows a diagram of a fifth example in accordance with one ormore embodiments of the invention. The example depicted in FIG. 7B maydepict an authentication and authorization operation. The example is notintended to limit the scope of the invention. The example systemdepicted in FIG. 7B may include fewer components than the systemsdepicted in FIGS. 1A-1C for the sake of brevity.

Turning to the example, consider a scenario in which a video camera (notshown) provides video data to an edge device (700). The edge device(700) includes a DPU (702) and edge persistent storage (704).

Initially, the DPU (702) obtains video data (706) from a video camera(not shown) [1]. After obtaining the video data (706), the DPU (702)applies the video data to the data analytics models of the videoprocessing engine (not shown) of the DPU (702) to generate video datachunks (708) and video processing engine outcomes (710) [2]. The videodata chunks (708) includes video data chunk A (708A) and video datachunk B (708B). The video processing engine outcomes (710) include frauddetection (710A) and facial recognition (710B). Following the generationof the video data chunks (708) and the video processing engine outcomes(710), the DPU (702) generates indexing metadata (712) and AA metadata(722) based on the video data chunks (708) and the video processingengine outcomes (710) [3]. The indexing metadata (712) includes streamID A (714A) and information associated with both video data chunks(708A, 708B). The information associated with video data chunk A (708A)includes video data chunk ID A (716A), start time A (718A), and end timeA (720A). The information associated with video data chunk B (708B)includes video data chunk ID B (716B) start time B (718B), and end timeB (720B). The AA metadata (722) includes AA metadata A (722A) and AAmetadata B (722B). AA metadata A (722A) includes authentication andauthorization information associated with video data chunk A (708A). Theauthentication and authorization information specifies that video datachunk A (708A) is associated with object ID A (724A), users associatedwith the AA metadata have full access, users with user ID A (726A)and/or group ID A (728A) may access video data chunk A (708A), and usersare authorized to only read video data chunk A (708A). AA metadata B(722B) includes authentication and authorization information associatedwith video data chunk B (708B). The authentication and authorizationinformation specifies that video data chunk B (708B) is associated withobject ID B (724B), users associated with the AA metadata have fullaccess, users with user ID B (726B) and/or group ID B (728B) may accessvideo data chunk B (708B), and users are authorized to read and write tovideo data chunk B (708B).

Then, the DPU (702) associates the indexing metadata (712) and the AAmetadata (722) with the video data chunks (708) by associating the videodata chunk IDs (716A, 716B) with each AA metadata (722A, 722B) [4]. Inthis example, fraud detection (710A), which is associated with user ID A(726A) and group ID A (728B), occurs in video data chunk A (708A) and isassociated with video data chunks ID A (716A), and facial recognition(710B), which is associated with user ID A (726A) and group ID A (728B),occurs in video data chunk B (708B) and is associated in video datachunk ID B (716B). Finally, the DPU (702) sends the video data chunks(708A, 708B) and copies of portions of the indexing metadata (712) andAA metadata (722) to the backup storage (730) and are stored in primarystorage (732) as processed primary storage video data (734). Theprocessed primary storage video data (734) includes video data chunk A(708A), video data chunk ID A (716A), start time A (718A), end time A(720A), video data chunk B (708B), video data chunk ID B (716B), starttime B (718B), and end time B (720B).

FIG. 8A shows a flowchart of method for performing a long term stitchingoperation in accordance with one or more embodiments of the invention.The method shown in FIG. 8A may be performed by, for example, a DPU(e.g., 104, FIG. 1B) of an edge device. Other components of the systemillustrated in FIG. 1A may perform all, or a portion, of the method ofFIG. 8A without departing from the invention. While various steps in theflowchart are presented and described sequentially, one of ordinaryskill in the relevant art will appreciate that some or all of the stepsmay be executed in different orders, may be combined or omitted, andsome or all of the steps may be executed in parallel.

In step 800, video data is obtained. In one or more embodiments of theinvention, the video data is obtained from a video camera. The videocamera may send a message to the peripheral interface of the edge devicethrough the local connection. The message may include a video file. Thevideo file may include video data. The video file may include otherand/or additional data without departing from the invention. Theperipheral interface may provide the video data to the DPU. The videodata may be obtained via other and/or additional methods withoutdeparting from the invention.

In another embodiment of the invention, a video camera streams the videodata to the peripheral interface of the edge device. In other words, thevideo camera transmits the video data through the local connection tothe peripheral device as a steady, continuous flow. The peripheraldevice may provide the video data to the DPU. The video data may beobtained via other and/or additional methods without departing from theinvention.

In step 802, the video data is processed to obtain video data chunks andvideo processing engine outcomes. In one or more embodiments of theinvention, the DPU applies data analytics model(s) (discussed above) ofthe video processing engine to the video data. The data analyticsmodel(s) may generate one or more video processing engine outcomesassociated with the video data. The video processing engine outcomes mayinclude, for example, facial recognition, fraud detection, and otherand/or additional video processing engine outcomes as discussed above.The data analytics model(s) may break up the video data into video datachunks associated with the one or more video processing engine outcome.Each video processing engine outcome may be associated with one or morevideo data chunks and each video data chunk may be associated with oneor more video processing engine outcomes. The data analytics model(s)may generate any number of video processing engine outcomes and dividethe video data into any number of video data chunks without departingfrom the invention. The video data may be processed to obtain video datachunks and video processing engine outcomes via other and/or additionalmethods without departing from the invention.

In step 804, retention and staging metadata is generated based on thevideo data chunks and the video processing engine outcomes. In one ormore embodiments of the invention, the DPU generates retention andstaging metadata using the video data chunks and the video processingengine outcomes. The DPU may generate or update a video stream metadataentry. The DPU may include retention and staging metadata in the videostream metadata entry. The DPU may generate and include retention andstaging information (discussed above) associated with the video datachunks in the retention and staging metadata. The DPU may includeretention and staging policies obtained from a user of the system. Theretention and staging policies may include retention periods and staginginformation for the video data chunks associated with the one or morevideo processing engine outcomes and the video processing engineoutcomes associated with each retention period and staging information.The DPU may compare the video processing engine outcomes associated withthe video data chunks with the video processing engine outcomes includedin the retention and staging policies and include retention periods andstaging information in the retention and staging metadata based on thecomparisons. The retention and staging metadata may be generated basedon the video data chunks and the video processing engine outcomes viaother and/or additional methods without departing from the invention.

In step 806, the retention and staging metadata is associated with thevideo data chunks. In one or more embodiments of the invention, the DPUupdates the video stream metadata entry associated with the video datachunks to associate the retention and staging metadata with the videodata chunks. The DPU may associate the video data chunk identifiersassociated with each video data chunk with each retention period andstaging information included in the retention and staging metadata. Forexample, the DPU may associate the video data chunk identifierassociated with a first video data chunk with a first retention periodand set staging information associated with the first video data chunk.The retention and staging metadata may be associated with the video datachunks via other and/or additional methods without departing from theinvention.

In step 808, the retention and staging metadata and video data chunksare stored in storage based on the retention and staging metadata. Inone or more embodiments of the invention, the DPU stores the retentionand staging metadata in the edge persistent storage of the edge deviceand the video data chunks in a backup storage. The DPU may also generatecopies of the retention and staging metadata and include the copies orthe retention and staging metadata with the video data chunks stored inthe backup storage. The DPU may send a message to the backup storagethrough the non-local connection. The message may include the video datachunks, the copies of the retention and staging metadata, and a requestto store the video data chunks and the copies of the retention metadatain the appropriate storages (i.e., primary storage, secondary storage,and/or archival storage) of the backup storage. In response to obtainingthe message, the backup storage may store each of the video data chunksand the copies of retention and staging metadata associated with eachvideo data chunk in the appropriate storage based on the retentionmetadata. The retention and staging metadata and the video data chunksmay be stored in appropriate storages based on the retention and stagingmetadata via other and/or additional methods without departing from theinvention.

In step 810, a determination is made as to whether all video data chunksare in archival storage. In one or more embodiments of the invention,each video data chunk stored in the backup storage is de-staged toarchival storage at some period of time as discussed above. The backupmanager of the backup storage may include the retention and stagingmetadata, and may de-stage the video data chunks to the archival storageaccording to the retention and staging metadata, which may specify allof the video data chunks in a video stream. The backup manager maymonitor the retention and staging metadata and the video data chunksstored in archival storage, and when all video data chunks of a videostream are de-staged to archival storage, the backup manager of thebackup storage may send a notification to the DPU. The notification mayinclude a message that includes a request to stitch together the videodata chunks. The DPU may wait any amount of time for the notificationfrom the backup manager of the backup storage. When the DPU obtains thenotification from the backup manager of the backup storage and confirmsthat the notification includes a message that all video data chunksassociated with a video stream are in archival storage, the DPU maydetermine that a notification that all video data chunks are in archivalstorage is obtained from the backup storage. The notification mayinclude a video stream identifier and storage locations for each videodata chunk associated with the notification. A determination may be madeas to whether all video data chunks are in archival storage via otherand/or additional methods without departing from the invention.

In one embodiment of the invention, the backup manager of the backupstorage may send a notification that a video data chunk was de-staged toa different storage. The DPU may update the retention and stagingmetadata to indicate that the video data chunk was de-staged to thedifferent storage. The DPU may monitor the retention and stagingmetadata to determine when all video data chunks associated with a videostream are stored in archival storage. If the retention and stagingmetadata indicates that all video data chunks are stored in archivalstorage, then the DPU may determine that all video data chunks arestored in archival storage. If the retention and staging metadata doesnot indicate that all video data chunks are stored in archival storage,then the DPU may determine that all video data chunks are not stored inarchival storage. A determination may be made as to whether all videodata chunks are in archival storage via other and/or additional methodswithout departing from the invention.

If it is determined that a notification that all video data chunks arein archival storage is obtained from a backup storage, then the methodproceeds to step 812. If it is that a notification that all video datachunks are in archival storage is not obtained from a backup storage,then the method proceeds to step 810 (i.e., the DPU waits until thenotification is received).

In step 812, the video data chunks are stitched together. The video datachunks may be stored in various storage locations and may be consider bythe backup storage manager as individual video data chunks. The DPU mayuse the retention and staging metadata and/or other metadata (i.e.,indexing metadata) to identify all of the video data chunks associatedwith the video stream identifier included in the retention and stagingmetadata and/or the other metadata. The DPU may obtain copies of thevideo data chunks from the backup storage and associate the video datachunks of the video data stream together to generate a video file. Thevideo file may include the video stream identifier and the video datachunks. The DPU may send the video file to the backup storage, whichstores the video file in archival storage in a manner such that thevideo data chunks are stored contiguously. The backup manager of thebackup storage may delete the individual video data chunks (not thevideo data chunks included in the video file) from archival storage. Thevideo data chunks may be stitched together via other and/or additionalmethods without departing from the invention.

In step 814, a determination is made as to whether the long termretention period has ended. In one or more embodiments of the invention,the DPU uses the retention and staging metadata to determine whether thelong term retention period has ended. As discussed above, the retentionand staging metadata includes the long term retention period associatedwith each video data chunk. The DPU may monitor the long term retentionperiods using a real-time clock, and when the long term retention periodmatches or is an earlier point in time than the time depicted by thereal time clock, the long term retention period has ended. If the longterm retention period matches or is an earlier point in time than thetime depicted by the real-time clock, then the DPU determines that thelong term retention period has ended. If the long term retention perioddoes not match or is a later point in time than the time depicted by thereal-time clock, then the DPU determines that the long term retentionperiod has not ended. A determination may be made as to whether the longterm retention period has ended via other and/or additional methodswithout departing from the invention.

If it is determined that the long term retention period has ended, thenthe method proceeds to step 816. If it is determined that the long termretention period has not ended, then the method proceeds to step 814.

In step 816, the video data chunks are deleted from archival storage. Inone or more embodiments of the invention, the DPU initiates the deletionof the video data chunks. The DPU may send a message to the backupstorage. The message may include the video data chunk identifiersassociated with each of the video data chunks. The message may alsoinclude a request to delete the video data chunks associated with thevideo data chunk identifiers. After obtaining the message, the backupmanager of the backup storage may delete the video data chunksassociated with the video data chunk identifiers from the archivalstorage. The video data chunks may be deleted from archival storage viaother and/or additional methods without departing from the invention.

The method may end following step 816.

FIGS. 8B-8C show diagrams of a sixth example in accordance with one ormore embodiments of the invention. The example depicted in FIGS. 8B-8Cmay depict a long term stitching operation. The example is not intendedto limit the scope of the invention. The example system depicted inFIGS. 8B-8C may include fewer components than the systems depicted inFIGS. 1A-1C for the sake of brevity.

Turning to the example and FIG. 8B, consider a scenario in which a videocamera (not shown) provides video data to an edge device (800). The edgedevice (800) includes a DPU (802) and edge persistent storage (804).

Initially, the DPU (802) obtains video data (806) from a video camera(not shown) [1]. After obtaining the video data (806), the DPU (802)applies the video data to the data analytics models of the videoprocessing engine (not shown) of the DPU (802) to generate video datachunks (808) and video processing engine outcomes (810) [2]. The videodata chunks (808) includes video data chunk A (808A) and video datachunk B (808B). The video processing engine outcomes (810) include frauddetection (810A) and facial recognition (810B). Following the generationof the video data chunks (808) and the video processing engine outcomes(810), the DPU (802) generates indexing metadata (812) and retention andstaging (RS) metadata (822) based on the video data chunks (808) and thevideo processing engine outcomes (810) [3]. The indexing metadata (812)includes stream ID A (814A) and information associated with both videodata chunks (808A, 808B). The information associated with video datachunk A (808A) includes video data chunk ID A (816A), start time A(818A), and end time A (820A). The information associated with videodata chunk B (808B) includes video data chunk ID B (816B) start time B(818B), and end time B (820B). The RS metadata (822) includes RSmetadata A (822A) and RS metadata B (822B). RS metadata A (822A)includes the retention period and staging information associated withvideo data chunk A (808A), in which fraud detection (810A) occurred. Theretention period specifies that video data chunk A (808A) may not bedeleted for ten years, and the staging information specifies that videodata chunk A (808A) is to be stored in a primary storage and thende-staged after a year. RS metadata B (822B) includes the retentionperiod and staging information associated with video data chunk B(808B), in which facial recognition (810B) occurred. The retentionperiod specifies that video data chunk B (808B) may not be deleted forten years, and the staging information specifies that video data chunk B(808B) is to be stored in an archival storage.

Then, the DPU (802) associates the indexing metadata (812) and the RSmetadata (822) with the video data chunks (808) by associating the videodata chunk IDs (816A, 816B) with each RS metadata (822A, 822B) [4]. Inthis example, fraud detection (810A), which is associated with RSmetadata A (822A), occurs in video data chunk A (808A). Therefore, videodata chunk ID A (816A) is associated with RS metadata A (822A). Facialrecognition (810B), which is associated with RS metadata B (822B),occurs in video data chunk B (808B). Therefore, RS metadata B (822B) isassociated with video data chunk ID B (816B). Finally, the DPU (802)sends the video data chunks (808A, 808B) and copies of portions of theindexing metadata (812) and RS metadata (822) to the backup storage(830). Video data chunk A (808A) and the indexing metadata (812) and RSmetadata (822) associated with video data chunk A (808A) are stored inprimary storage (832) as processed primary storage video data (836)based on RS metadata A (822A). The processed primary storage video data(834) includes video data chunk A (808A), video data chunk ID A (816A),and RS metadata A (822A). Video data chunk B (808B) and the indexingmetadata (812) and RS metadata (822) associated with video data chunk B(808B) are stored in archival storage (834) as processed archivalstorage video data (838) based on RS metadata B (822B). The processedarchival storage video data (838) includes video data chunk B (808B),video data chunk ID B (816B), and RS metadata B (822B).

Turning to FIG. 8C, after a year, the backup storage (830) de-stagesvideo data chunk A (808A) from primary storage (832) to archival storage(834) [6]. As a result, the processed archive storage video data (838)now includes video data chunk A (808A), video data chunk ID A (816A),and RS metadata A (822A). After video data chunk A (808A) is de-stagedfrom primary storage (832) to archival storage (834), the backup storage(830) sends a notification to the DPU (802) that all video data chunksassociated with stream ID A (814A) are stored in archival storage [7].In response to obtaining the notification from the backup storage (830),the DPU stitches together video data chunk A (808A) and video data chunkB (808B) [8]. As a result, video data chunk A (808A) and video datachunk B (808B) are represented in the archival storage (834) as a singlevideo stream (represented by the dashed line depicted in FIG. 8C.

FIG. 9A shows a flowchart of a method for performing a contextualstitching operation in accordance with one or more embodiments of theinvention. The method shown in FIG. 9A may be performed by, for example,a DPU (e.g., 104, FIG. 1B) of an edge device. Other components of thesystem illustrated in FIG. 1A may perform all, or a portion, of themethod of FIG. 9A without departing from the invention. While varioussteps in the flowchart are presented and described sequentially, one ofordinary skill in the relevant art will appreciate that some or all ofthe steps may be executed in different orders, may be combined oromitted, and some or all of the steps may be executed in parallel.

Turning to FIG. 9A, in step 900, a contextual stitching trigger event isidentified. In one or more embodiments of the invention, the DPUidentifies an anomaly as a contextual trigger event. As discussed above,during processing of video data, the DPU applies data analytics model(s)to video data. The data analytics model(s) may generate video processingengine outcomes associated with anomalies. For example, a videoprocessing engine outcome may be detection of a fraudulent activity,security breach, and other and/or additional types of anomalies withoutdeparting from the invention. The DPU may identify the aforementionedvideo processing engine outcomes that result in detections of anomaliesas contextual trigger events. The DPU may identify one or more indexingattributes associated with the contextual trigger events. A contextualstitching trigger event may be identified via other and/or additionalmethods without departing from the invention.

In one or more embodiments of the invention, a contextual trigger eventis obtained from a user of the system. A user of the system may send amessage to the DPU. The message may include a request for contextualstitching of video data chunks. The message may include one or moreindexing attributes associated with the request. The DPU may identifythese requests from users as contextual stitching trigger events. Acontextual trigger event may be identified via other and/or additionalmethods without departing from the invention.

In step 902, video data chunks, contextual metadata, indexing metadata,and AA metadata associated with the contextual stitching trigger eventare identified. In one or more embodiments of the invention, the DPUuses the indexing attribute(s) included in or identified in thecontextual stitching trigger event to identify video data chunks,contextual metadata, indexing metadata, and AA metadata associated withthe contextual stitching trigger event. As discussed above, indexingattributes may specify information regarding of video data chunkcontents such as a person, date and time, location, and other and/oradditional information regarding video data chunk contents withoutdeparting from the invention. The DPU may search the video streammetadata entries stored in edge persistent storage for indexing metadataassociated with the indexing attribute(s) associated with the contextualstitching trigger event. The DPU may identify indexing metadataassociated with the indexing attribute of the contextual trigger event.The DPU may obtain the identified indexing metadata, and the contextualmetadata and AA metadata associated with the identified indexingmetadata from edge persistent storage. The DPU may identify and obtainvideo data chunks associated with the identified indexing metadata fromthe backup storage(s). Video data chunks, contextual metadata, indexingmetadata, and AA metadata associated with the contextual stitchingtrigger event may be identified via other and/or additional methodswithout departing from the invention.

In one or more embodiments of the invention, the DPU sends messages toother DPUs of other edge devices to identify and obtain video datachunks, indexing metadata, contextual metadata, and AA metadataassociated with the contextual trigger event. All, and or a portion, ofthe video data chunks, indexing metadata, contextual metadata, and/or AAmetadata associated with the contextual stitching trigger event may bestored in other DPUs and/or backup storages. The messages may includethe indexing attribute(s) associated with the contextual stitchingtrigger event and a request for video data chunks, indexing metadata,contextual metadata, and AA metadata associated with the indexingattribute(s). In response to obtaining the requests, the DPUs mayidentify and obtain all, or a portion, of the indexing metadata,contextual metadata, AA metadata, and the video data chunks associatedwith the indexing attribute(s) via methods discussed above and send theidentified indexing metadata, contextual metadata, AA metadata, andvideo data chunks to the DPU that identified the contextual triggerevent. Video data chunks, indexing metadata, contextual metadata, and AAmetadata associated with the contextual trigger event may be identifiedvia other and/or additional methods without departing from theinvention.

In step 904, a virtual blob is generated using the video data chunks,contextual metadata, indexing metadata and the AA metadata. In one ormore embodiments of the invention, DPU uses the virtual blob generatoralong with the video data chunks, contextual metadata, indexingmetadata, and the AA metadata to generate a virtual blob. The virtualblob generator may generate a virtual blob file as discussed above. Thevirtual blob file may include the AA metadata, contextual metadata, andindexing metadata associated with the video data chunks. The virtualblob file may be used to stitch together the video data chunks and toverify a user's authentication and authorization information. The DPUmay include an expiration timestamp in the virtual blob file and storethe virtual blob in edge volatile storage of the edge device. A virtualblob may be generated using the video data chunks, contextual metadata,indexing metadata, and the AA metadata via other and/or additionalmethods without departing from the invention.

In step 906, a determination is made as to whether a playback request isobtained from a user. In one or more embodiments of the invention, theuser of the system sends a message to the DPU. The message may include aplayback request associated with the virtual blob. The message mayinclude the indexing attribute(s), and/or other indexing metadata thatmay be used by the DPU to identify the virtual blob associated with theplayback request. The message may also include authentication andauthorization information associated with the user. If the DPU obtains amessage that includes a playback request associated with the virtualblob, then the DPU may determine that a playback request is obtainedfrom a user. If the DPU does not obtain a message that includes aplayback request associated with the virtual blob, then the DPU maydetermine that a playback request is not obtained from a user. The DPUmay wait for a playback request until the expiration timestamp includedin the virtual blob is exceeded. In such a scenario, the DPU may deletethe virtual blob from edge volatile storage. A determination may be madeas to whether a playback request is obtained from a user via otherand/or additional methods without departing from the invention.

If it is determined that a playback request is obtained from a user,then the method proceeds to step 908. If it is determined that aplayback request is not obtained from a user, then the method proceedsto step 906 (i.e., the DPU waits until a playback request is received).

In step 908, a determination is made as to whether the user matches theAA metadata. In one or more embodiments of the invention, the DPUcompares the users authentication and authorization information with theAA metadata included in the virtual blob. The user authentication andauthorization information may include a user identifier and/or a groupidentifier. The DPU may compare the user identifier and/or groupidentifier included in the user authentication and authorizationinformation with the user identifier and/or group identifier included inthe AA metadata in the virtual blob. If the user identifiers and/orgroup identifiers match, then the DPU may determine that the usermatches the AA metadata. If the user identifiers and/or groupidentifiers do not match, then the DPU may determine that the user doesnot match the AA metadata. A determination may be made as to whether theuser matches the AA metadata via other and/or additional methods withoutdeparting from the invention.

If it is determined that the user matches the AA metadata, then themethod proceeds to step 910. If it is determined that the user does notmatch the AA metadata, then the method proceeds to step 912.

In step 910, the video data chunks are encoded into a single stream andplayback is initiated for the user. In one or more embodiments of theinvention, the DPU uses the virtual blob to encode the video data chunksinto a single stream. The DPU may generate a video file and includes allthe video data chunks using the indexing metadata and contextualmetadata included in the virtual blob. The video file may be played bythe user. The DPU may send the video file and a message that includes arequest to initiate playback of the video file to the user. The videodata chunks may be encoded into a single stream and playback may beinitiated for the user. The video data chunks may be encoded into asingle stream and playback may be initiated via other and/or additionalmethods without departing from the invention.

The method may end following step 910.

In step 912, a text transcript associated with the video data chunks isgenerated. In one or more embodiments of the invention, the DPU uses thecontext generator to generate a text transcript associated with thevideo data chunks. The DPU may apply the context generation model(s)included in the context generator to the contextual metadata and videodata chunks. The context generation model(s) may generate a texttranscript associated with the video data chunks. The text transcriptmay be a text file that includes a textual summary of the video datachunks. A text transcript associated with the video data chunks may begenerated via other and/or additional methods without departing from theinvention.

In step 914, the text transcript is provided to the user. In one or moreembodiments of the invention, the DPU sends a message to the user. Themessage may include the text transcript associated with the video datachunks. The text transcript may be provided to the user via other and/oradditional methods without departing from the invention.

The method may end following step 914.

FIG. 9B shows a diagram of a seventh example in accordance with one ormore embodiments of the invention. The example depicted in FIG. 9B maydepict a contextual stitching operation. The example is not intended tolimit the scope of the invention. The example system depicted in FIG. 9Bmay include fewer components than the systems depicted in FIGS. 1A-1Cfor the sake of brevity.

Turning to the example and FIG. 9B, consider a scenario in which a user(not shown) requests for video data from an edge device (900). The edgedevice (900) includes a DPU (902) and edge persistent storage (904).

Initially, the DPU (902) obtains a request for video data from a user(not shown) of the system. The request may be a request for video datachunks associated with person B (916B). The DPU (902) identifies therequest as a contextual stitching trigger event [1]. After identifyingthe contextual stitching trigger event, the DPU (902) identifies andobtains indexing metadata (906), contextual metadata (918) (whichincludes person A (916A) as happy (918A) and person B (916B) as nervous(918B)), and AA metadata (920) associated with the contextual stitchingtrigger event [2]. The indexing metadata (906) includes stream ID A(908A) and information associated with the video data chunks (936A,936B, 936C). The information associated with video data chunk A (936A)includes video data chunk ID A (910A), start time A (912A), and end timeA (914A). The information associated with video data chunk B (936B)includes video data chunk ID B (910B) start time B (912B), and end timeB (914B). The information associated with video data chunk C (936C)includes video data chunk ID C (910C) start time C (912C), and end timeC (914C). The indexing metadata (906) obtained by the DPU (902) onlyincludes indexing information associated with video data chunk B (936B)and video data chunk C (936C) since person B (916B) is associated withvideo data chunk B (936B) and video data chunk C (936C).

The DPU (902) then identifies and obtains video data chunk B (936B) andvideo data chunk C (936C) stored in primary storage (932) of the backupstorage (930) as processed primary storage video data (934) [3]. Theprocessed primary storage video data (934) includes video data chunk A(936A), video data chunk ID A (910A), start time A (912A), end time A(914A), video data chunk B (936B), video data chunk ID B (910B) starttime B (912B), end time B (914B), video data chunk C (936C), video datachunk ID C (910C) start time C (912C), and end time C (914C). The DPU(902) then generates a virtual blob (940) using video data chunk B(936B), video data chunk C (936C), indexing metadata (906), contextualmetadata (918), and AA metadata (920) [4]. After generating the virtualblob (940), the DPU (902) obtains a playback request, and determinesthat the user authentication and authorization information included inthe playback request matches the AA metadata (918) included in thevirtual blob (940) [5]. In response to the determination, the DPU (902)encodes video data chunk B (936B) and video data chunk C (936C) into asingle video file and provides the video file to the user [6].

FIG. 10A shows a flowchart of a method for performing a right to beforgotten operation in accordance with one or more embodiments of theinvention. The method shown in FIG. 10A may be performed by, forexample, a DPU (e.g., 104, FIG. 1B) of an edge device. Other componentsof the system illustrated in FIG. 1A may perform all, or a portion, ofthe method of FIG. 10A without departing from the invention. Whilevarious steps in the flowchart are presented and described sequentially,one of ordinary skill in the relevant art will appreciate that some orall of the steps may be executed in different orders, may be combined oromitted, and some or all of the steps may be executed in parallel.

Turning to FIG. 10A, in step 1000, an RTF request is obtained from auser. In one or more embodiments of the invention, a user of the systemmay send a message to the DPU. The message may include a RTF request.The message may also include one or more indexing attributes (i.e., oneor more people) associated with the RTF request. An RTF request may beobtained via other and/or additional methods without departing from theinvention.

In step 1002, video data chunks, contextual metadata, and indexingmetadata associated with the RTF request are identified. In one or moreembodiments of the invention, the DPU uses the indexing attribute(s)included in the RTF request to identify video data chunks, contextualmetadata, and indexing metadata associated with the RTF request. Asdiscussed above, indexing attributes may specify information regardingof video data chunk contents, such as a person. The DPU may search thevideo stream metadata entries stored in edge persistent storage forindexing metadata associated with the indexing attribute(s) associatedwith the RTF request. The DPU may identify indexing metadata associatedwith the indexing attribute(s). The DPU may obtain the identifiedindexing metadata, and the contextual metadata associated with theidentified indexing metadata from edge persistent storage. The DPU mayidentify and obtain video data chunks associated with the identifiedindexing metadata from the backup storage(s). Video data chunks,contextual metadata, and indexing metadata associated with the RTFrequest may be identified via other and/or additional methods withoutdeparting from the invention.

In one or more embodiments of the invention, the DPU sends messages toother DPUs of other edge devices to identify and obtain video datachunks, indexing metadata, and contextual metadata, and with the RTFrequest. All, and or a portion, of the video data chunks, indexingmetadata, and/or contextual metadata associated with the RTF request maybe stored in other DPUs and/or backup storages. The messages may includethe indexing attribute(s) associated with the RTF request and a requestfor video data chunks, indexing metadata, and contextual metadataassociated with the indexing attribute(s). In response to obtaining therequests, the DPUs may identify and obtain all, or a portion, of theindexing metadata, contextual metadata, and the video data chunksassociated with the indexing attribute(s) via the methods discussedabove and send the identified indexing metadata, contextual metadata,and video data chunks to the DPU that obtained the RTF request. Videodata chunks, indexing metadata, and contextual metadata associated withthe RTF request may be identified via other and/or additional methodswithout departing from the invention.

In step 1004, a determination is made as to whether any negativeconnotations are associated with the video data chunks. In one or moreembodiments of the invention, the DPU identifies contextual metadata andapplies the data analytics model(s) of the video processing engine tothe video data chunks to obtain video processing engines to generatevideo processing engine outcomes to determine if the video data chunksare associated with any negative connotations. The contextual metadatamay include contextual attributes that depict negative characteristicsof people included in video data chunks (e.g., nervous, false pretensemade, etc.). The video processing engine outcomes may include negativevideo processing engine outcomes such as fraud detection, securitybreach, and any other negative video processing engine outcomes withoutdeparting from the invention. If the video processing engine outcomesand/or contextual metadata are associated with negative connotations,then the DPU may determine that negative connotations are associatedwith the video data chunks. If the video processing engine outcomes andcontextual metadata are not associated with any negative connotations,then the DPU may determine that no negative connotations are associatedwith the video data chunks.

If it is determined that negative connotations are associated with thevideo data chunks, then the method proceeds to step 1008. If it isdetermined that no negative connotations are associated with the videodata chunks, then the method proceeds to step 1006.

In step 1006, the video data chunks associated with the RTF request aredeleted. In one or more embodiments of the invention, the DPU deletesthe video data chunks from edge storage and the backup storage(s). TheDPU may identify the video data chunks associated with the RTF requestusing the indexing metadata associated with the video data chunks andthe indexing attribute(s) included in the RTF request. The DPU may senda message to the backup storage(s) to delete all video data chunksassociated with the RTF request. In response to obtaining the request,the backup storage(s) may delete the video data chunks. The video datachunks may be deleted via other and/or additional methods withoutdeparting from the invention.

The method may end following step 1006.

In step 1008, a text transcript associated with the video data chunks isgenerated. In one or more embodiments of the invention, the DPU uses thecontext generator to generate a text transcript associated with thevideo data chunks. The DPU may apply the context generation model(s)included in the context generator to the contextual metadata and videodata chunks. The context generation model(s) may generate a texttranscript associated with the video data chunks. The text transcriptmay be a text file that includes a textual summary of the video datachunks. A text transcript associated with the video data chunks may begenerated via other and/or additional methods without departing from theinvention.

In step 1010, the text transcript is provided to the user. In one ormore embodiments of the invention, the DPU sends a message to the user.The message may include the text transcript. The text transcript may beprovided to the user via other and/or additional methods withoutdeparting from the invention.

In step 1012, a determination is made as to whether the user clears thenegative connotations associated with the video data chunks. In one ormore embodiments of the invention, the user sends a message to the DPUthat indicates whether the negative connotations are cleared. Themessage may include a flag, or a special bit, that when set, indicatesthat the negative connotations are cleared. If the flag is set, the DPUmay determine that the user clears the negative connotations associatedwith the video data chunks. If the flag is not set, the user maydetermine that the user does not clear the negative connotationsassociated with the video data chunks. A determination may be made as towhether the user clears the negative connotations associated with thevideo data chunks via other and/or additional methods without departingfrom the invention.

In step 1014, the RTF request is rejected. In one or more embodiments ofthe invention, the DPU sends a message to the user. The message mayinclude a notification that the RTF request is rejected. As a result,the DPU may not delete the video data chunks associated with the RTFrequest. The RTF request may be rejected via other and/or additionalmethods without departing from the invention.

The method may end following step 1014.

FIG. 10B shows a diagram of an eighth example in accordance with one ormore embodiments of the invention. The example depicted in FIG. 10B maydepict a RTF operation. The example is not intended to limit the scopeof the invention. The example system depicted in FIG. 10B may includefewer components than the systems depicted in FIGS. 1A-1C for the sakeof brevity.

Turning to the example and FIG. 10B, consider a scenario in which a user(not shown) requests for video data associated with a RTF request bedeleted from an edge device (1000). The edge device (1000) includes aDPU (1002) and edge persistent storage (1004).

Initially, the DPU (1002) obtains an RTF request from a user (not shown)of the system [1]. The RTF request may be a request for video datachunks associated with person B (1016B). After obtaining the RTFrequest, the DPU (1002) identifies and obtains indexing metadata (1006)and contextual metadata (1020) (which includes person A (1016A) as happy(1020A) and person B (1016B) as nervous (1020B)) [2]. The indexingmetadata (1006) includes stream ID A (1008A) and information associatedwith the video data chunks (1036A, 1036B, 1036C). The informationassociated with video data chunk A (1036A) includes video data chunk IDA (1010A), start time A (1012A), and end time A (1014A). The informationassociated with video data chunk B (1036B) includes video data chunk IDB (1010B) start time B (1012B), and end time B (1014B). The informationassociated with video data chunk C (1036C) includes video data chunk IDC (1010C) start time C (1012C), and end time C (1014C). The indexingmetadata (1006) obtained by the DPU (1002) only includes indexinginformation associated with video data chunk B (1036B) and video datachunk C (1036C) as person B (1016B) is associated with video data chunkB (1036B) and video data chunk C (1036C).

The DPU (1002) then identifies and obtains video data chunk B (1036B)and video data chunk C (1036C) stored in primary storage (1032) of thebackup storage (1030) as processed primary storage video data (1034)[3]. The processed primary storage video data (1034) includes video datachunk A (1036A), video data chunk ID A (1010A), start time A (1012A),end time A (1014A), video data chunk B (1036B), video data chunk ID B(1010B), start time B (1012B), end time B (1014B), video data chunk C(1036C), video data chunk ID C (1010C), start time C (1012C), and endtime C (1014C). After obtaining video data chunk B (1036B) and videodata chunk C (1036C), the DPU (1002) applies video data chunks B (1036B)and video data chunk C (1036C) to the data analytics model(s) of thevideo processing engine and obtains a video processing engine outcome(1040). The video processing engine outcome is fraud detection (1040A),which is associated with person B (1016B). The DPU (1002) determinesthat there is negative connotations associated with video data chunk B(1036B) and video data chunk C (1036C) due to the fraud detection(1040A) [4]. The DPU (1002) generates a text transcript associated withvideo data chunk B (1036B) and video data chunk C (1036C) and providesthe text transcript to the user. The user does not clear the negativeconnotations [5]. The DPU (1002) rejects the RTF request and does notdelete video data chunk B (1036B) and video data chunk C (1036C) [6].

As discussed above, embodiments of the invention may be implementedusing computing devices. FIG. 11 shows a diagram of a computing devicein accordance with one or more embodiments of the invention. Thecomputing device (1100) may include one or more computer processors(1102), non-persistent storage (1104) (e.g., volatile memory, such asrandom access memory (RAM), cache memory), persistent storage (1106)(e.g., a hard disk, an optical drive such as a compact disk (CD) driveor digital versatile disk (DVD) drive, a flash memory, etc.), acommunication interface (1112) (e.g., Bluetooth interface, infraredinterface, network interface, optical interface, etc.), input devices(1110), output devices (1108), and numerous other elements (not shown)and functionalities. Each of these components is described below.

In one embodiment of the invention, the computer processor(s) (1102) maybe an integrated circuit for processing instructions. For example, thecomputer processor(s) may be one or more cores or micro-cores of aprocessor. The computing device (1100) may also include one or moreinput devices (1110), such as a touchscreen, keyboard, mouse,microphone, touchpad, electronic pen, or any other type of input device.Further, the communication interface (1112) may include an integratedcircuit for connecting the computing device (1100) to a network (notshown) (e.g., a local area network (LAN), a wide area network (WAN) suchas the Internet, mobile network, or any other type of network) and/or toanother device, such as another computing device.

In one embodiment of the invention, the computing device (1100) mayinclude one or more output devices (1108), such as a screen (e.g., aliquid crystal display (LCD), a plasma display, touchscreen, cathode raytube (CRT) monitor, projector, or other display device), a printer,external storage, or any other output device. One or more of the outputdevices may be the same or different from the input device(s). The inputand output device(s) may be locally or remotely connected to thecomputer processor(s) (1102), non-persistent storage (1104), andpersistent storage (1106). Many different types of computing devicesexist, and the aforementioned input and output device(s) may take otherforms.

One or more embodiments of the invention may be implemented usinginstructions executed by one or more processors of the data managementdevice. Further, such instructions may correspond to computer readableinstructions that are stored on one or more non-transitory computerreadable mediums.

One or more embodiments of the invention may be implemented usinginstructions executed by one or more processors of the data managementdevice. Further, such instructions may correspond to computer readableinstructions that are stored on one or more non-transitory computerreadable mediums.

One or more embodiments of the invention may improve the operation ofone or more computing devices. More specifically, embodiments of theinvention relate to generating AA metadata based on video processingengine outcomes through AA operations when initially processing videodata by a DPU of an edge device. Further, in various embodiments of theinvention, AA metadata may be used by the DPU to store and manage videodata in accordance with authentication and authorization requirementsspecified by the AA metadata, which may increase the efficiency ofstoring and managing video data in the system. Additionally, the AAmetadata may specify whether video data chunks are associated with legalhold. The DPU may use the AA metadata to ensure video data chunks complywith legal hold requirements, thereby mitigating the risk of deletingvideo data chunks associated with legal holds.

The problems discussed above should be understood as being examples ofproblems solved by embodiments of the invention disclosed herein and theinvention should not be limited to solving the same/similar problems.The disclosed invention is broadly applicable to address a range ofproblems beyond those discussed herein.

While the invention has been described above with respect to a limitednumber of embodiments, those skilled in the art, having the benefit ofthis disclosure, will appreciate that other embodiments can be devisedwhich do not depart from the scope of the invention as disclosed herein.Accordingly, the scope of the invention should be limited only by theattached claims.

What is claimed is:
 1. A method for processing video data, the methodcomprising: obtaining, by a data processing unit (DPU) of an edgedevice, video data; processing the video data to obtain video datachunks and video processing engine outcomes; generating authenticationand authorization (AA) metadata based on the video data chunks and thevideo processing engine outcomes; associating the AA metadata with thevideo data chunks based on the video processing outcomes; and storingthe AA metadata and the video data chunks.
 2. The method of claim 1,wherein storing the AA metadata and the video data chunks comprises:storing the AA metadata in persistent storage of the edge device; andstoring the video data chunks and a copy of the AA metadata in a backupstorage.
 3. The method of claim 1, further comprising: following thestoring the AA metadata and the video data chunks: obtaining a deletionrequest associated with the video data chunks; making a determinationthat the AA metadata indicates that the video data chunks are associatedwith a legal hold; and in response to the determination, rejecting thedeletion request.
 4. The method of claim 1, wherein processing the videodata comprises applying at least one data analytics models to the videodata.
 5. The method of claim 4, wherein the at least one data analyticsmodel generates the video data chunks and the video processing engineoutcomes.
 6. The method of claim 1, wherein the video data comprises atleast one selected from a group consisted of: video data obtained from avideo camera; and video data stored in a backup storage.
 7. The methodof claim 2, wherein the video camera is connected to the edge devicewith a local connection and the backup storage is connected to the edgedevice with a non-local connection.
 8. A system for processing videodata, comprising: a backup storage operatively connected to an edgedevice comprising: primary storage, secondary storage, and archivalstorage; a video camera operatively connected to the edge device andconfigured to generate video data; the edge device comprising a dataprocessing unit (DPU), wherein the DPU is configured to perform amethod, the method comprising: obtaining, by a data processing unit(DPU) of an edge device, video data; processing the video data to obtainvideo data chunks and video processing engine outcomes; generatingauthentication and authorization (AA) metadata based on the video datachunks and the video processing engine outcomes; associating the AAmetadata with the video data chunks based on the video processingoutcomes; and storing the AA metadata and the video data chunks.
 9. Thesystem of claim 8, wherein obtaining the video data comprises obtainingthe video data obtained from the video camera.
 10. The system of claim8, wherein obtaining the video data comprises obtaining the video datastored in the backup storage.
 11. The system of claim 8, wherein thevideo camera is operatively connected to the edge device with a localconnection and the backup storage is operatively connected to the edgedevice with a non-local connection.
 12. The system of claim 11, whereinthe local connection is a local wireless connection.
 13. The system ofclaim 11, wherein the local connection is a local wired connection. 14.The system of claim 11, wherein the non-local connection is a networkconnection over a wide area network.
 15. A non-transitory computerreadable medium comprising computer readable program code, which whenexecuted by a computer processor enables the computer processor toperform a method for processing video data, the method comprising:obtaining, by a data processing unit (DPU) of an edge device, videodata; processing the video data to obtain video data chunks and videoprocessing engine outcomes; generating authentication and authorization(AA) metadata based on the video data chunks and the video processingengine outcomes; associating the AA metadata with the video data chunksbased on the video processing outcomes; and storing the AA metadata andthe video data chunks.
 16. The non-transitory computer readable mediumof claim 15, wherein storing the AA metadata and the video data chunkscomprises: storing the AA metadata in persistent storage of the edgedevice; and storing the video data chunks and copies of the AA metadatain a backup storage.
 17. The non-transitory computer readable medium ofclaim 15, wherein the method further comprising: following storing theAA metadata and the video data chunks: obtaining a deletion requestassociated with the video data chunks; making a determination that theAA metadata indicates that the video data chunks are associated with alegal hold; and in response to the determination: rejecting the deletionrequest.
 18. The non-transitory computer readable medium of claim 15,wherein processing the video data comprises applying at least one dataanalytics models to the video data.
 19. The non-transitory computerreadable medium of claim 18, wherein the at least one data analyticsmodel generates the video data chunks and the video processing engineoutcomes.
 20. The non-transitory computer readable medium of claim 16,wherein the video data comprises at least one selected from a groupconsisted of: video data obtained from a video camera; and video datastored in a backup storage.